Académique Documents
Professionnel Documents
Culture Documents
Project Walkthrough
The purpose of the project walkthrough is to give students an opportunity to discuss their
preliminary findings regarding system requirements with the instructor. The walkthrough
should be scheduled with the instructor after submitting project proposal and before the
interim report is due. The students should have drafts of their DFD, process and data
models ready at the time of the walkthrough. The walkthrough will typically take 30-45
minutes and will involve a 10 minute presentation by the team and a 20-30 min of
informal discussion.
Interim Report (System Requirements Document)
The interim report will contain a description of user requirements for the proposed
system and a conceptual design for your system:
Title page and table of contents
Executive summary
Discussion of the current situation
Project vision and scope
Description of system requirements with references to the appendix
Process description
Data description
Non-functional requirements
Interface requirements
Security
Performance
Technological constraints
Definition of work for Stage 2 (description of forms and reports, updated
schedule)
Appendix including supporting diagrams
Final Report (Design Document)
Title page and table of contents
Executive summary
Project vision and scope
Summary of functional and data requirements
Proposed acquisition strategy and system architecture
Interface design (overall approach, dialog diagram or equivalent, generic form
designs with explanations)
Relational database prototype in MS Access, including forms and reports for
adding, modifying and querying data.
Implementation plan (system selection issues, test plan, post-implementation
review plan)
Proof of concept UI prototype using technology of your choice, unless otherwise
approved by the instructor (you will need to include description and screen-shots
in your report), including. Your prototype should have at least 7 screens (forms or
reports) and at least 2 programs. Your prototype does not need to have DB
connectivity but needs to be sufficient to demonstrate the flow of your application
to a potential user.
A user manual for the UI prototype (may be concise, but professionally done).
Team Presentation
Your team presentation is designed for you to be able to practice your client
communication skills. You should consider the top management of your client
organization to be your audience.
The presentation should last no more than 10 min
The presentation should cover
Description of the organizational need and summary of system
requirements
Solution overview (emphasize how it will address the problem and what
are the benefits. Quantify benefits if possible)
Prototype demo
Implementation discussion
Summary/lessons learned
Submit printout of your slides before the presentation
Project timeline
Due dates for all the deliverables are indicated in the syllabus.