Systems Analysis and Design (INFO 1113)

Final Project Report

TASKS:

Submit formal Final Project Report

Final Project Report: Submit Final Project Report that covers the following items:

Cover Page (Course Name, Section Number , Title of the project, Full Names of
Team Members, Student Ids, Emails, Date )
Table of contents
Executive Summary (See http://www.ehow.com/how_16566_write-executivesummary.html, http://en.wikipedia.org/wiki/Executive_summary)
Introduction: introduces the project (that sums up the whole report), and that
whole report has to do with the topics introduced in this section. In your
introduction you have to introduce all the ideas you are going to cover in your
report.
Requirements: Appropriate elements covering sections 1 to 10 and content from
Requirements and Techniques from the above sections. You need to have
proper structured English for your paragraphs. Each paragraph has to have a topic
sentence; this topic sentence is what the paragraph is about.
a. Prepare the thorough description of Project Requirements complete
with functional and non-functional requirements.
b. Create fully developed Use-Case diagram and corresponding Use-Case
Descriptions. (Use the template in Figure 4-11 page 176).)
c. Create class diagram complete with associations and multiplicity,
attributes and operations (See Chapter 5).
d. Develop one sequence and corresponding communication diagram for
one use case related to your project (See Chapter 6). Do not use Log in
use case.
e. Choose one of the classes developed in (c) above. Create a contract for
each method in that class. See sample in Appendix A.
f. Create a method specification for each method in the class you chose
for question (e) above. See sample in Appendix A.

g. Design the interface structure by preparing a Windows Navigation

diagram (WND) based on the essential use cases that will identify the
main interfaces that need to be built and show how they relate to each
other. (See Chapter 10 - Figure 10-8 , page 425)
h. Create an interface prototype for the project that will be used by the
customers. I suggest you start by drawing a storyboard on paper before
you try to build the prototype. You need to decide exactly how much
information goes on a single screen, and then where it should be laid out.
(See Chapter 10 - Figures 10-11 to 10-13 in pages 430-431) . Use any tool
you are comfortable with (Visio, Dreamweaver, MS-Word, Visual
Studio). Design all screens/reports for your project
i. Review class diagram in (c) above. Determine which objects belonging to
which classes must be persisted (Determine persistent classes). Define
detail attributes, the values of which must be saved in database. Create
relational database tables that could be stored in Access database.
Make sure all relations are normalized up to Third Normal Form (3NF)
(See Chapter 9).
j. Optional (Bonus):Implement the Database using Access and create few
appropriate queries(different type of queries). Name the database as
Final_Project.accdb

Project Experience:
o Turn in a document that enumerates honestly what worked and didn't work
well with your team project. This document is a group consensus (only
one document per group), but can identify differences of opinion -- where
some people like a practice and others didn't.
Conclusion: sums up everything that you mentioned in the introduction.
Work Cited: this is a bibliography of all the texts that you referred to in
your report.

SUBMISSIONS:
1. Write a professional formal report outlining your work.
2. Report must have proper heading, section numbers, page numbers etc.
3. Name the Report as Final_Project.docx
4. Submit the project on Moodle (one submission per group).

APPENDIX A: Sample Contract and Method Specification

(Read Chapter 8)
Contract specification

Method Name: getIngredients()

Class Name: Menu

Clients (Consumers): Report

Associated Use Cases:
Order supplies
Description of Responsibilities:
Determine all the ingredients required to prepare this menu.
Arguments Received:
None.
Type of Value Returned:
List: all ingredients required for this menu item.
Preconditions:

Postconditions:

ID:

Method specification

Method Name: getIngredients()

Class Name: Menu

ID:

Contract ID:

Programmer: J. Doe

Date Due: 5 July

Programming Language: Java

Triggers/Events:
Arguments Received:
(Data Type)

Notes:

None (n/a)
Messages Sent & Arguments
Passed:
ClassName.MethodName:

Data Type:

Ingredient.getName()

String

Notes:

Arguments Returned:
Data Type:

Notes:

Ingredient list
(Java.util.Collection)

A collection (Java-defined interface) of Strings, where each

element is an ingredient of the menu instance

Algorithm Specification:
1.
2.
3.
4.

Create an empty instance of a Collection

For each ingredient in the Menu instance
thisIngredientName Ingredient.getName()
Return the Collection instance

Misc. Notes: