I uploaded the presentation in the files.. & also uploaded the project here in case you want to modify it cause I will be out of cairo for a couple of days.. (Check the files in, in case u will be working on the TFS cause there are some things modified)
Nice Working with All of you guyz... I really did enjoy it :)
Wednesday, August 29, 2007
Sunday, August 26, 2007
Meeting Minutes
The meeting minutes if todays meeting is uploaded 26/8/2007 please check it out for the assigned tasks. thanks team. GOOOOOOOOOO GradStats :D
Tuesday, August 21, 2007
Status report
The updated status report is now uploaded. Sorry for being late but we wanted to finish some tasks first.
Monday, August 20, 2007
Sunday, August 19, 2007
Tasks
The current progress:
1- MasterPage & CSS file are done.
2- Requirement document tested for verification (updated version 1.3 uploaded now)
3- 60% of the Reporting Services are investigated (generated some demo reports on the Server & on my local machine)
4- Development of prototypes (UI) started & 50% done so far. [using AJAX]
Please update this post with the progress in the BL & DL..
1- MasterPage & CSS file are done.
2- Requirement document tested for verification (updated version 1.3 uploaded now)
3- 60% of the Reporting Services are investigated (generated some demo reports on the Server & on my local machine)
4- Development of prototypes (UI) started & 50% done so far. [using AJAX]
Please update this post with the progress in the BL & DL..
Saturday, August 18, 2007
Front End
Al salamo 3alikom wa ra7mato Allah wa barakatoh :)
I'm supposed to be implementing the front end GUI, but I have a little problem. I don't have the front end prototypes, or anything else indicating what I should be doing. Untill something shows up, I'll be making ASSUMPTIONS.
I'm supposed to be implementing the front end GUI, but I have a little problem. I don't have the front end prototypes, or anything else indicating what I should be doing. Untill something shows up, I'll be making ASSUMPTIONS.
Tuesday, August 14, 2007
Team Roles
Team Coordinator: Mina
Schedule Owner: Mohab
DB Agent: Heba
Requirements analyser: Omar
Testing officer: Roaa
Schedule Owner: Mohab
DB Agent: Heba
Requirements analyser: Omar
Testing officer: Roaa
Monday, August 13, 2007
Vote..
Guyz, I made a poll to vote about the master page design [at the sidebar].. Vote now ;)
(& please write comments too)
(& please write comments too)
Sunday, August 12, 2007
About RSS Feed
The RSS is not working due to permission issues (cause the blog access is restricted to the authors only -elly howa e7na-)
I made another solution, I automated the operation of sending mails to all of us in case of any comments or updates on the blog.. I think that will do in shaa Allah..
I made another solution, I automated the operation of sending mails to all of us in case of any comments or updates on the blog.. I think that will do in shaa Allah..
Master Page Design
Friday, August 10, 2007
Requirements document
Hi,
I just want to add to what Heba has said that the requirements document is also uploaded under the name GradStats_Requirements Specification_1_1
I just want to add to what Heba has said that the requirements document is also uploaded under the name GradStats_Requirements Specification_1_1
Thursday, August 9, 2007
Deliverables Comments (Part 2)
First of all I would like to admire the team’s efforts and I have a good feeling that we will be literally the “TITANS” :)
Now for my comments and tips for the current version of the deliverables, they are as follows:
1. Documents Naming Convention
· From my working experience I found out that it is recommended as best practice to maintain a naming convention for the project documents to simplify the recognition of the document and its content directly from its name.
· Usually we use the following convention ProjectName_DocumentName. Feel free to use it or change it depending on your usage.
· Some examples for this convention are as follows:
i. GradStats_RequirementSpecification.doc
ii. GradStats_ProjectPlan.mpp
iii. GradStats_TimeSheet.xls
iv. GradStats_MinutesOfMeeting_20070809.doc
· As you can see using this convention will simply tell you the content of the document by simply reading the name or even the date as in the minutes of meeting example.
2. Developing Class Diagram in Visio
· We need to develop the class diagram to represent the pages in the system as we agreed upon earlier. Try to figure out all the available pages in the system and start implementing the class diagrams for each one of them.
· This will help us later through the code and prototype development
3. Developing ERD under SQL Server
· The ERD that I found on the blog is more of a class diagram rather than a database ERD. I would advise if we use the SQL Server to create the tables directly and extract the ERD by drawing the tables diagram instead to save time and effort later.
4. Using Table of Contents (TOC) features in MS Word.
· I frankly admired the document structure and the level details written inside this document, and I noticed while going through the pages that we need to add a dynamic TOC that would reflect the document sections and its corresponding pages without the hassle of updating it manually each time a part of the document is change.
· To help you with this I thought I would give you a reference on how to add a TOC to your document which will make your life easier in the future updates inside the document:
i. In case you are using older version of Office: http://malektips.com/word_2003_0002.html
ii. For Office 2007: https://www.uwec.edu/help/Word07/AUTO-toc.htm
I am also attaching the project plan as promised, and I need you to ask the schedule owner to start assigning the tasks to the available resources in order to start working on the project plan.
Once again, good job team and keep up the good work.
Now for my comments and tips for the current version of the deliverables, they are as follows:
1. Documents Naming Convention
· From my working experience I found out that it is recommended as best practice to maintain a naming convention for the project documents to simplify the recognition of the document and its content directly from its name.
· Usually we use the following convention ProjectName_DocumentName. Feel free to use it or change it depending on your usage.
· Some examples for this convention are as follows:
i. GradStats_RequirementSpecification.doc
ii. GradStats_ProjectPlan.mpp
iii. GradStats_TimeSheet.xls
iv. GradStats_MinutesOfMeeting_20070809.doc
· As you can see using this convention will simply tell you the content of the document by simply reading the name or even the date as in the minutes of meeting example.
2. Developing Class Diagram in Visio
· We need to develop the class diagram to represent the pages in the system as we agreed upon earlier. Try to figure out all the available pages in the system and start implementing the class diagrams for each one of them.
· This will help us later through the code and prototype development
3. Developing ERD under SQL Server
· The ERD that I found on the blog is more of a class diagram rather than a database ERD. I would advise if we use the SQL Server to create the tables directly and extract the ERD by drawing the tables diagram instead to save time and effort later.
4. Using Table of Contents (TOC) features in MS Word.
· I frankly admired the document structure and the level details written inside this document, and I noticed while going through the pages that we need to add a dynamic TOC that would reflect the document sections and its corresponding pages without the hassle of updating it manually each time a part of the document is change.
· To help you with this I thought I would give you a reference on how to add a TOC to your document which will make your life easier in the future updates inside the document:
i. In case you are using older version of Office: http://malektips.com/word_2003_0002.html
ii. For Office 2007: https://www.uwec.edu/help/Word07/AUTO-toc.htm
I am also attaching the project plan as promised, and I need you to ask the schedule owner to start assigning the tasks to the available resources in order to start working on the project plan.
Once again, good job team and keep up the good work.
Deliverables Comments
Team, I am impressed with the work done and efforts put into the deliverables so far. I have quickly went through the documents and have few comments that I will write back to you in a documented format to be considered in the next change.
I liked the Titans logo very much, if you guys made it yourself then let me raise a hat for you, job well done :)
I will consult with Helmy to see whether he has any further comments to add to mine before sending it to you. But till then good job everyone and keep up the good work.
I liked the Titans logo very much, if you guys made it yourself then let me raise a hat for you, job well done :)
I will consult with Helmy to see whether he has any further comments to add to mine before sending it to you. But till then good job everyone and keep up the good work.
Dear Supervisors
Hi Samy and Ahmed,
we did our first drafts of the deliverables, and some other documents that you wanted. however, we need your feedback on these documents as soon as possible to know if we are on the right track or not. Also, we can get a clear understanding of what a class diagram for this project should be like. what we were able to do is a system architecture rather than a class diagram. please provide us with the feedback as soon as you can so that we can start working on the second drafts. thanks a lot for your time.
we did our first drafts of the deliverables, and some other documents that you wanted. however, we need your feedback on these documents as soon as possible to know if we are on the right track or not. Also, we can get a clear understanding of what a class diagram for this project should be like. what we were able to do is a system architecture rather than a class diagram. please provide us with the feedback as soon as you can so that we can start working on the second drafts. thanks a lot for your time.
Wednesday, August 8, 2007
Requirements Document
http://www.4shared.com/file/21629028/58d49bfb/GS_001.html
Sorry for inconvenience, but I couldn't use the widget.
GS stands for "Grad Stats"
Please comment on the document.
Sorry for inconvenience, but I couldn't use the widget.
GS stands for "Grad Stats"
Please comment on the document.
Files
I added a widget at the sidebar of the blog to share the files, anyone can download the files & also you can upload files using the following user name & password..
Username :: gradstats@gmail.com
Password :: gradproj
The currently added files contain::
1- ERD of the project
2- System Architecture Diagram
3- Meeting Minutes Sheet for today
Username :: gradstats@gmail.com
Password :: gradproj
The currently added files contain::
1- ERD of the project
2- System Architecture Diagram
3- Meeting Minutes Sheet for today
Tuesday, August 7, 2007
Agenda 1
This is the agenda of tomorrow's meeting
12:00 - 12:45 : discussing the requirements in the requirements document
12:45 - 01:15 : discussing the ER diagram
01:15 - 01:45 : discussing the class diagram
01:45 - 02:00 : concluding the meeting with what's required to be done
hope to see you all.
12:00 - 12:45 : discussing the requirements in the requirements document
12:45 - 01:15 : discussing the ER diagram
01:15 - 01:45 : discussing the class diagram
01:45 - 02:00 : concluding the meeting with what's required to be done
hope to see you all.
Greetings Team
I would like to grab this chance to welcome every member of our great team and I wish you all good luck in the project.
I also wanted to tell you that I am excited to be working with you and hope that the project goes smooth without bumpy rides (which never happens, but at least the hope is there) :).
Again I would like to greet you again and looking forward to working with all of you.
I also wanted to tell you that I am excited to be working with you and hope that the project goes smooth without bumpy rides (which never happens, but at least the hope is there) :).
Again I would like to greet you again and looking forward to working with all of you.
Subscribe to:
Comments (Atom)
