Project Milestones

Proposal (Milestone1)

Your Milestone1 should be 3-5 pages in length. Study the sample proposal distributed. Your proposal must have the following components:

Identification

a. Title (short, but meaningful)

b. Project category (A&D, Life cycle, Research/Survey, Tool)

c. Name (List all team members)

d. Term and date

1. The problem statement

1.1 Goals of the system

1.2 Context and importance of the system

1.3 Scope

of the system

1.3.1 In-scope

(Scope to be included)

1.3.2 Out-scope (Scope that will not be included)

2. Requirements

2.1 Functional Requirements

of the system

2.2 Data Requirements

of the system

2.3 Business Rules and Logic

2.4 Non-Functional Requirements such as usability, reliability, interface, performance, security, etc.

2.5 Other important assumptions

3. Examples of system input/output scenarios.

4. Knowledge Acquisition

· How you will learn about the problem?

· Is this a real problem, or one you have conjured up?

5. Software and/or hardware involved in developing specifications or implementation (if you are working on Life Cycle projects)

6. Proposed Deliverables and the work plan

7. Known References

Examples of system input/output scenarios in VRS (Video Rental System):

· Example Input scenarios:

· A customer rents 2 DVDs and 1 Video tape

· A customer returns items, but one of them is overdue

· A customer pays by a credit card

· A customer pays with a gift certificate

· A customer wants to cancel a rent after completing the transaction

· A customer calls the store to reserve a DVD

· A staff adds a new DVD title

· A staff adds new DVDs of pre-added title

· Example Output scenarios:

· At the end of each day, the system prints a summary of all the transactions by item types and payment types

· System alters all rents which are over-due by more than 10 days or $20.

The following shows the typical contents of the final format of the A&D project report. Except those items marked as Optional, all other items are mandatory. Those in blue colors are mandatory and those in red are optional.

Example of A&D Project Documentation

Title page (title of your topic, all the member names, term identification) Contents (section and page number)

Introduction (1 page summary of the whole project)

System Analysis

(1) The Problem Statement

1.1 Goal,

1.2 Context and Importance,

1.3 Scope
1.3.1 In-scope

1.3.2 Out-Scope

(2) Requirements

2.1 Functional Requirements
2.2 Data Requirements
2.3 Business Rules and Logic

2.4 Non-Functional Requirements such as interface, performance, reliability, etc.

2.5 Other Important Assumptions

(3) Use Case Model

3.1 Actors and Their Goals

3.2 Use case diagram

3.3 Overview section of all use cases

3.4 Use case description in template (one primary use case per team member. Put each member name for each use case description)

3.5 Activity diagrams of the chosen primary use case (optional)

3.6 Validation & Discussion (modeling decisions, alternative solutions to the model and other important clarification)

(4) Class Model

4.1 Class diagram with classes and major attributes (Called Analysis class diagram or domain model)

4.2 Selected Class definitions for those whose class names are not intuitive

4.3 Selected Association definitions for those whose association names are not intuitive

4.4 Validation & Discussion (modeling decisions, scenarios used, alternative solutions to the model and other important clarification)

System Design

(5) A system sequence diagram of the chosen use case (Each member should have his/her own system sequence diagram for the chosen use case.)

(6) The sequence diagrams that expand the system sequence diagram. (Each member should have his/her own full sequence diagram(s) for the chosen use case.)

(7) A state diagram (optional)

(

8

) Design Class diagram with all the attributes and operations ( Rem em b er t h at V isio d oes n o t sav e b o t h an aly sis class d iagram an d d esign

class d iagram sep arately . Hen ce, y ou h av e t o sav e t h em in t o tw o d if f eren t f ile s .)

(9) Class diagrams with packages and dependencies (optional)

(10) Validation & Discussion

Physical Design

(11) Component diagrams (optional)

(12) Deployment diagrams (optional)

(13) ERD (optional)

(14) Relational Database Schema

(15) Discussion between differences between ERD and analysis class diagram (Optional)

(16) Data Dictionary (optional)

(17) Validation & Discussion

Applications Design

· Screen flow diagrams and Dialog flow diagram (optional)

· Screen prototypes (optional)

· Report prototypes (optional)

· Discussion

· Sample C++ or Java Class Specification (in logical form, optional)

(16) Evaluation of Analysis & Design (evaluation of the project, domain, diagrams, the UML and the modeling tools used, quality of the specification)

(17) Summary and Lessons learned

(18) References

(19) Appendix

A. Division of the work among team members

B. Experience (Individual member must write separately lessons learned )

C. Unsolved problems (Any questions related to A&D activities you still have)

Validation and Discussion
should include:

· Explanation of the model so that readers can understand the model better rather than just a diagram

· Comparing multiple alternatives of the model and the justification of your chosen model

· Summarizing any remaining problems or issues regarding to the model

Evaluation of Analysis & Design
should include

Evaluate the domain you selected, complexity of the problem, methods used, UML itself, Rose or Visio, team work, things to do more if you have more time, and things to do differently if you redo the project, etc

Incremental Documentation

A final comment: the best method for documentation is incremental documentation.

DO NOT WAIT UNTIL YOU COMPLETE YOUR SYSTEM. It is very easy to

forget the fresh idea you had by the time you finish your project. Write whenever you have some material that you need to include in your final report.

Grading Guidelines:

· Problem Statement, use case diagram, class diagram, design class diagrams, and relational schema are
graded together for all the members
. That is, all the members will

8

get the same grade for these components. Hence, all the members must collaborate to develop them.

· Use case description, system SQD, and full SQD are
graded individually
. That is, each member will get a different grade for these components as each member is responsible for his or her own use case description system SQD, and full SQD. Members of a team can help develop/review those model components of other team members, but each member is responsible for his/her own component for them. Note that SSQD and SQD must be based on the use case description chosen by each member.

· For other project types, you should submit a progress report when A&D projects submit use case diagrams and class diagrams for review.

Project Deliverable and Submission

All the projects must submit a soft copy:

(1) Create a report by consolidating all the materials into a single Word file including the final report, diagrams, programs, output, etc as outlined above. That is, copy and paste all the diagrams of all the members into the final report (Milestone 4). Organize them in a reviewer-friendly manner. Add page numbers.

(2) Create one zip file that includes the report file in Word, all the diagram (e.g., visio) files, or any other related files (e.g, codes, screen shots, output) used in the project.

(3) Use the naming convention of 355-18W-P-yourLastName_or_team_name- acronym-of-your-project.zip (e.g., 355-18W-PCCS.zip). That is, by reading your zip file name, I should be able to easily identify your term and project topic.

(4) Submit project and peer evaluation form to Blackboard Assignment folder of Week

10. Use the naming convention of 355_18W_PEF_yourLastName_and_team_name-acronym-of-your-project.zip (e.g., 355_18W_PEF_Name_PCCS )

Examplesof Milestone 1, INFO355, Song

1

INFO 355: Systems Analysis II

Winter 2016

Project Category: Analysis and Design

Title: A Simplified Accounting Management System (SAMS)
Milestone 1

George Bush, Bill Clinton, Hilary Clinton, and Barack Obama

1. Problem Description
A small local accounting company would like to create a simplified accounting management

system (SAMS). SAMS will keep track of only those concepts that are related to calculation

of income of the office such as clients, billable items, payments, and invoices. SAMS,

however, will not include other office-related activities such as employee payrolls, purchasing

office supplies, office expenses such as

travel cost, or other complex tax-related matters.

In

the office, there are two types of clients, individual clients or business clients. Individual

clients usually pay once a year when they pick up their annual tax returns. Business clients

usually pay the regular monthly service charge once a month for their routine service.

Business clients may also pay to the office when they receive a special service such as tax

audit, special tax preparation, license application, etc. The monthly service charge is different

from a client to another, depending on the business type, volume of transactions, and other

factors.

In this office, an item that is charged to clients is called a billable item. The fee for some

billable items (e.g., applying for a tax ID) are pre-determined at a fixed price and used

consistently. The fees for these pre-determined billable items can be changed only by the owner

of the office. However, the fees for some billable items are determined by case by case by the

owner of the office. The office sends invoices to business clients once a month by computing

the total outstanding balances by summing up all the unpaid or partially billable items. Clients

may pay fully, partially, or may not pay on time. Some clients may also pay in advance the fees

of several months or even one year. The office receives only cash, checks, or credit cards.

SAMS should also be able to generate several reports such as “show the payment history of a

client,” “show clients with all the outstanding balances,” “show the total billing of this

month”, ‘show the total payments of this month”, etc.

A billable item is initially called “uninvoiced”. Once an invoice for the billable item is

sent out, the status becomes “invoiced”. The item could also be discounted or cancelled.

A client can be searched by one of three ways: either by client number, by last name, or by

just browsing the client list. The system shall be password-protected. SAMS has the three

type sof users- accountants, secretary, and the owner of the office. Accountants can create

new clients, edit client information, and create new billable items. The secretary in SAMS can

do any operation the accountants can do, except creating new billable items. In addition, the

secretary will generate invoices, reports, and enter payments. Discounts or cancellation of

billable items, however, can only be done by the owner.

IN-Scope: clients, billable items, invoices, payments, reports

OUT-Scope: employee payrolls, purchasing office supplies, office expenses such as

travel cost, or other complex tax-related matters.

Examples of Milestone 1, INFO355, Song

2

2. Requirements
2.1 Functional Requirements

1. Maintain client

a. Create client

b. Edit client (Update monthly service charge)

c. Delete client

2. Search for clients by one of three ways

a. by Client Number

b. by Last Name (Speed searching)

c. by Browsing

d. Sort clients by some criteria

3. Keep track of billable items of a client

a. Add monthly service charge

b. Add the special service charges

c. Discount a billable item (only by owner)

d. Cancel a billable item (only by owner)

e. Change the states of a billable item

5. Generate Invoices

a. View invoice

b. Print invoice

c. Save invoice

d. Convert into PDF

6. Manage payments

a. Enter payment

b. View payment

c. Edit payment

d. Delete payment

e. Print receipt

7. Generate reports

a. Show payment history of a client

b. Show clients with all the outstanding balances

c. Show the total billing of this month

d. Show the total payments of this month

c. Generate monthly/annual report for a client

8. Generate mailing labels

9. User login and log out

10. Quit/save

11. Meta functions (by Administrator or Owner)

a. Maintain users

a.1 add users

a.2 delete users

a.3 edit user profile

b. Maintain standard (reference) billable items

b.1. Create a specification for a new billable item with name and charge

b.2. Edit specification of a billable item

b.3. Delete a specification of a billable item

c. Backup the data

d. Import/export the data

Examples of Milestone 1, INFO355, Song

3

e. Maintain Help features

2.2 Data Requirements
1. Client

Client#, First Name, Last Name, middle initial, Client type, Business Address and Home

Address, Business Phone, Home Phone and Mobile phone, Client Business Type, total

outstanding balance, first business date, monthly service charge

2. Billable Items

Item#, description, fee, date entered, initial amount, balance, status, discount, discountdate

3. Invoice

Invoice number, billing date, billing amount, due date

4. Payment

Payment number, payment amount, payment date, payment type, bank name, check number,

CC info (last 4 digits, name, billing address, security digits)

5. User

First Name, Last Name, middle initial, ID, PW, userGroup, beginDate, status, recentUsedDate

6. Special Service Rate

Service number, service name, default_fee

2.3 Business Rules and Logic

Business Rules: They are rules on events and the system.

1. The fee for billable item is determined and can be changed only by the owner of the office

2. Only business clients receive an invoice once a month.

3. A cancelled billable item will not be deleted, but marked as “cancelled” and this value must

not be included into the invoice.

4. Pre-defined billable item is picked up from the special service rate table except the monthly

service charge.

5. A payment is applied to from old billable items first and then to newer billable items

6. The SAMS data will need to be backed up to an external device (USB, HD, cloud) daily at

3AM.

Constraints on Data and Objects: These are rules on data and objects.

1. Identify mandatory fields (e.g., Client number, first name, and last name)
2. Client type is either Individual or Business
3. Payment type is either Cash, Check, or Credit Card.
4. Valid values of Status of Billable Item = {uninvoiced, invoiced, partially paid, fully paid,

cancelled}

5. For a new billable item, status is set to “uninvoiced”, balance = initial amount.
6. The outstanding balance will reflect the total summation of balances of all the billable

items except those whose status is marked as “cancelled” or “fully paid”

7. When a payment is entered, the initial amount stays the same; the balance will be reduced
by the amount of the payment.

8. The Status state of the billable items will be changed automatically from “uninvoiced” to
other status by operations.

9. A client number consists of 6 digits.
10. All input email address must have @ symbol.
11. Passwords must be at least 8 characters and contain at least 1 number or a special symbol.

Examples of Milestone 1, INFO355, Song

4

2.4 Non-Functional Requirements

 Usability:
a) The system will be a screen-based GUI application.
b) Menus should be organized in a hierarchical manner.
c) The entry found after searching should be highlighted.
d) Must include a menu bar at the top
e) Must include a log off function in the upper right-hand side of the screen
f) All data deletion needs to have a confirmation dialog.
g) Business clients and individual clients should be flagged with different colors.
h) SAMS put in idle for 10 minutes are locked and must be opened with a password.
i) Menus should be grayed out if the user does not have a privilege to use.
j) Display alert message if a mandatory data is not entered.
k) Display invoices through a template for consistency.
l) Fields should be able to be resized.
m) Required fields should be indicated
n) Data are entered through forms; forms are displayed fully on the screen and should

not require no or minimum scrolling

o) Entries found after searching should be highlighted
p) Help options with FAQ should be available

 Reliability
a) Should support multiple users simultaneously
b) SAMS should be able to handle at least 0.1 million clients and 1 million

transactions for client

c) Backup should be done daily
d) SMAS should include error prevention. For example, if the user wants to

delete client information, a dialog box should appear, asking if the user is

completely sure that he or she wants to delete the information.

 Performance
a) All searches/sortings should be completed in approximately 1 second

 Security
a) All users must log-in with an ID and password
b) Three consecutive failures in log-in put the ID in hold for 5 minutes.
c) Password recovery should be available.
d) The system will automatically time out if the user has not entered a selection

in a certain amount of time.

e) There will be 3 groups of users.
 Group 1 is accountants. Ensure that Group1 users can create new clients, edit

client and create new billable items

 Group 2 is secretary. Ensure that Group 2 can do what Group 1 users can do,
except creating billable items.

o Ensure that Group 2 users can also generate invoice, reports, and enter
payments

Examples of Milestone 1, INFO355, Song

5

 Group 3 is the owner. Ensure that Group 3 users have all the privileges of Group 1
and 2. Only Group 3 users can delete clients, discount or cancel billable items.

 System environment

a) The system will be implemented in a LAN environment running Windows Business
Server 2011.

b) SQL Server 2012 Enterprise Edition will be used as a backend database.
c) Sufficient network bandwidth needs to be available.