CS 620 Software System Design - Final Project

Over the course of the semester, we have seen the various aspects of how of system is designed and developedfor your semester project, you will apply those topics to reverse engineer a website of your choosing

So what exactly do you need to do

First, you must decide if you are going to work alone or in a groupI will take groups up to THREE peoplekeep in mind, the work that you will have to turn in will vary based on the number of people in the groupthe bottom line is that whether you are working along or with a group, everyone will have the same amount of work to doyou will not do more work because you are in a group, and you will not do less work because you work alonethe advantage to working in a group is that you have someone to discuss things with and work with

Second, you must select a website that you would like to work withmake it something that you like and are interested init will make the project that much more interesting to you and in many ways, it will make it easier for youonce you have selected a site, you need to submit for me to approvewebsites will be approved on a first come first served basisso get these in as early as possibleI would recommend that you submit to me a first choice and a second choicethis way, in the event a different team selected your website, there is a better chance that you will not lose time

Keep in mind also that I will only accept one of a specific type of websitefor example, I will only accept one bank or one airlineso research carefullybut make sure you get these in as quickly as possible

Once your team and your website has been approved, it is time to take a deeper dive into the requirements of your website, and how the system flows and operatesyou will have THREE deliverables for this projectthey are as follows:

Project Definition Document

System Model Document

Component Model Document

Lets take a look at each one of these in more detail

Project Definition Document

A Project Definition Document acts as a contract between the business and the IT organization that is building the systemit speaks to the requirements of the system and the expectations of all the stakeholdersit is the one document that is the reference point for all future development

Keep in mind that in real life this document CAN and is often updatedbut only after the proposed changes are reviewed and approved by all the stakeholdersfor the purposed of this project, there will be NO changes to the original document

All of the deliverables are based on topics reviewed in the weekly Power Pointsyou can also find these topics in SWEBOKuse both of these as references for the information that you need to provide

What you should NOT do is look for these exact items on the internet and do a copy/pasteI expect the documents to be IN THE FORMAT THAT WAS REVIEWED IN CLASSif you give me information in any other format, you will receive a ZERO

I have listed below EXACTLY what I am looking foryou must follow this outlineif there are items not in this outline that you would like to include you must get approval from me FIRSTif you do not get my approval and you include things that I did not ask for, you will lose points

You must provide the following:

Project Definition

What are we building?...

Project scope

Project Deliverables

What are the deliverables?...

Needs to be specific enough so that everyone has the same expectations of what is being developed

Identification of Stakeholders

Who is the client?...

Who are we?...

Who is the project sponsor?...

Who are the end users?

Who are the external stakeholders?

Functional requirements

Statements of services the system should provide, how the system should react to particular inputs and how the system should behave in particular situations

May state what the system should not do

Non-functional requirements

Constraints on the services or functions offered by the system such as timing constraints, constraints on the development process, standards, etc.

Often applies to the system as a whole rather than individual features or services

Domain requirements

Constraints on the system from the domain of operation

Non-Functional Classifications

Product requirements: Requirements which specify that the delivered product must behave in a particular waye.g. execution speed, reliability, etc.

Organizational requirements: Requirements which are a consequence of organizational policies and procedurese.g. process standards used, implementation requirements, etc

External requirements: Requirements which arise from factors which are external to the system and its development processe.g. interoperability requirements, legislative requirements, etc

Ethnography

System Model Document

Based on your approved project and scope (Assignment 1), you must produce the following:

Context DFD 1 per project

Level 0 DFD 1 per project

Use Case Model 2 per person on the team

Use Case Natural Language Description 1 per person on the team

Sequence Diagram 2 per person on the team

Simple Object Class Diagram with Associations 1 per person on the team

Activity Model 2 per person on the team

Component Models

Based on your approved project and scope (Assignment 1), you must produce the following:

Component Model 2 per person on the team

Resuse Component Model- 2 per person on the team