Previous course: Project 2- 1415CT

Before you start....
You need to identify your project and recognize the problem. This means identifying the problem and recommending solutions as well as thinking about how you can implement the solution as project.

Pre-Analysis Phase [1week: due date week5]
          project nature, why is this 
project important? (i.e. how the project can be useful for the problem). 

          states the general goals of your project and the main tasks accomplished by this project. [Use numbered list and make sure your statements either 
start by verbs or nouns] 

          people or systems who benefit from using this project. [Give a brief description of each user, also identify end users and administrators] 

          A Gantt chart that shows: 


• When exactly the project is going to be completed
• Each part of the SDLC

• The details about all task to be performed (such details include: task name, when it will be started ,when it will be finished it's predecessors ...etc

Analysis Phase [1week: due date week6]
           detailed steps of how information was 
gathered, including any questionnaires or interview questions. It is better to interview all type of users and learn how currently process is working. [Note: all collected answers should be included in appendix C]. 

           the specific areas covered by the project. [Scope is a statement that defines the boundaries of the project. It tells not only what will be done but also what In the information systems industry, scope is often referred to as a functional specification] 

           explain what sort of challenges you see that may affect on the timeline of project and how you can overcome those challenges. [Read here ] 

          Resources needed: list all software and hardware components that will be needed to complete the project. 

 
Design Phase [2weeks: due date week 8]
          Draw detailed use case diagram [ identify in detail each actor] 

          Draw ER diagram 

          Draw Schema diagram 

          Draw class diagram [ identify real-worlds entities as well as software components] 

          Draw sequence diagram 

 
Implementation Phase [3 weeks: week 11 to13] 

           Implement database using MS-SQL/MS-Access 

           Implement application using VB.Net 

           Link application with the database 

           Use other software if needed 

 
 
Testing Phase [2 weeks: week14 &15]
           Within your group, each member needs to try the project and suggest improvements, 
then the whole team work on fixing and debugging. 

           When the project is complete, it needs to be installed on the target’s computer and wait 
for their feedback. 

           Keep updating and fixing the project while using it. 

 
User Manual [1 week: week 16] 

 All screens snapshots and clear steps for each user of the system.
References
 References for any used Books, papers and/or websites
Appendices
           Project Source Code 

           Weekly meeting (reports and/or assignments) 

           The collected answers from questionnaires and/or interviews 

           other 

 

-----------------*-----------------*-------------------

group distribution