Scribd
Upload
49 views1 page

Project I Requirements

Students registered in Project 1 are required to present a project design document that is between 5 to 20 pages long and follows a specific structure. This includes sections for an abstract, main goals, functionality, intended users, challenges, technology to be used, market potential or open source significance, requirements specification, use case modeling with diagrams, interface snapshots, and references. They must also give a 30-minute seminar on their project.

Uploaded by

Yousseff Moo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
49 views1 page

Project I Requirements

Students registered in Project 1 are required to present a project design document that is between 5 to 20 pages long and follows a specific structure. This includes sections for an abstract, main goals, functionality, intended users, challenges, technology to be used, market potential or open source significance, requirements specification, use case modeling with diagrams, interface snapshots, and references. They must also give a 30-minute seminar on their project.

Uploaded by

Yousseff Moo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd

To all Students registered in Project 1:

You are required to present the following document and give a 30-min
seminar on your project

Project Phase I Document

Write a project design document ( 5 – 20 pages ) with the following structure:


 Cover page containing name of project, team member, and advisors
 Abstract (between 100 and 150 words)
 Main goals – what is the project about
 Main functionality and characteristics
 Intended users and key usability goals (that is, how users will benefit from
your project)
 Challenges that you may encounter during the project’s development
 Intended technology, e.g., platform, languages, libraries, tools, etc.
 Market Potential or Open Source Significance (between 250 and 500
words) — if applicable to your project. Address the following:
o Market potential, commercial promise, or open source value
o Evidence of user interest (provide references)
o Social and environmental impact, if applicable
 Notes on similar/related products (provide references)
 Requirements specification: functional and non-functional requirements,
prioritized on 3 levels, as complete as possible.
 Use case modeling:
o Use case diagram: between 4 and 20 detailed use cases.
 Sequence diagrams: at least 5 sequence diagrams for the 5 major use
cases of the system.
 Initial snapshots of the system’s user interface: at least four snapshots,
with brief descriptions (but no more than 8 snapshots as detailed GUI
design will be part of P-II).
 List of references:
o At least four reference articles, with brief descriptions (40 to 70
words each) summarizing the article and showing how the
reference articles helped your project will be required.
o At least three related websites with useful resources.

You might also like