Explore

W23 Class W22 Mad5234 Assignment 1 Implementing Unified Process

High level description of the Purpose and Learning Outcomes of this Assignment:

In this Assignment, you will do the design and implementation of a College Enrollment System with the emphasis on the Software Planning and Design Elements.

Understand that creating high quality, trustable software doesn’t have by accident. We need to put many pieces in order to make it happen.

You can’t test your way out of a bad design.

The quality has to be baked into the foundations of your design.

Which means you need:

A quality design process (implemented with Unified Process)

Quality Testing Plan for things you could not foresee at design time.

(Beyond the scope of A1, but in the real world you need a bug tracking system. In A2 you will make your own Bugzilla).

Date Due January 17.

Your work will be graded out of a possible max score of 100 points.

Table

Table

ITEM

Weight

Comments

Notes

Software Specification Document — This includes SQM. Domain mapping to Range Graph.

Open

UML Design Overall

Open

Requirements Document

Open

Use Cases

Open

UML Design and Diagrams

Open

Tracability Matrix

Open

Test plan and execution — You must write JUNIT tests.

Open

There are no rows in this table

⁠

Grading Rubric:

What your Hand In for this Assignment is:

The URL to your Latex Document.

Each team:

Make a simple text file:

Team members’ names

Team Name : save your file as TeamName.docx

URL for your

Overleaf.com⁠

Latex Document

Upload your Team Info File to:

⁠

https://www.dropbox.com/request/gG0JzSu1oVHNuAl1s9PZ⁠

⁠

The back story of this assignment is the case study of South West Airlines and the failure of their scheduling system:

⁠

https://www.evernote.com/shard/s323/sh/d53bee04-f47d-2996-2e4c-7874155f4440/7c56b467f192e68c86e8335ca55315ce⁠

⁠

The business domain for this assignment is: The College Enrollment System

What are you going to deliver by the End:

User Stories: what should your CES do

Requirements Document: R01 The System Shall ....

Domain / Range Graph

SQM ( 4 to 6 )

Some factors to think about when you are writing SCQ:

Cost of failure/ or non performance of the software

Use Cases

UML diagrams: CID, OID

Class Interaction Diagram: purpose of this is to compose our classes and achieve our goals of high cohesion and low coupling

Object-Interaction Diagram: shows the method choreography of connections between objects.

Write Java Code and a SQLite DB to implement your Application

Tractability Matrix

How you will deliver this:

As a Latex document, optionally with a TRELLO board to help your team brain storm and organize the content.

Learning Outcomes:

Deliver a Unified process work flow to realize a simple application - The College Enrollment System (or another business domain)

To develop an application that you can use to experiment with:

Writing an SSD:

Description of the Application

User Stories => Requirements Document

Domain and Range of the Application

Software Quality Metrics

Writing a Project Plan

Create Use Cases

Create UML

Write the Code to implement the UML

Consider your data storage

What you are to do:

Based on our discussion about unified process, start to deliver your project.

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.