[Systems Development Project] [Project Deliverables]

SYSTEMS DEVELOPMENT PROJECT

OVERVIEW

A Sacramento-area client has hired your project team to develop a web based Information System which will automate one or more business functions. You will conduct all activities and prepare all deliverable products associated with the development process. At the conclusion of your study, you will prepare a comprehensive, high-quality project report containing your results. You will also design and program a working prototype model of your system using the programming language of your choice.

PROJECT INITIATION

Locate a company or agency that is interested in either automating a manually based information system or enhancing its current computer-based system. You may choose any type of organization (company or agency). If you choose a small company, cover a fairly wide range of business functions. If you choose a medium- to large-sized company, confine your scope to a more narrowly defined business application (e.g., customer billing and collection). It is better to have a deeper, more comprehensive analysis of a narrow-sized application scope. 

Explain to your client that your project team is willing to help them define their requirements and build a new system. They can use your study for either custom development or software package selection. Your consulting services could easily cost your client $20,000. You are willing to provide this service free in return for the client's cooperation for the project. 

Perform a quick feasibility analysis to ensure that the potential project is viable and complete the SystemScope.doc. Here are some things to consider: 

  • Your Use Case Diagram must have at least three meaningful processes
  • Your project must result in deliverable software in one of the following forms: 
    • Automated replacement of current manual system
    • Substantial reprogramming of an existing automated system
    • New automated interface to be placed on existing automated system
    • Other (by prior approval)
  • Your project must be web based (we will further discuss the architecture)
  • DBMS must be MySQL (unless the instructor approves a different DBMS)
  • I permit students to work on a project for their employer under the following assumptions: 
    • The entire group supports this project
    • The client understands that the entire team will be involved in the development process (interviews, e-mail, prototyping, programming, etc) and the client cannot be involved in assigning tasks for the group
    • The student that works for the client, will not be the primary contact with that client
    • This project is not part of the student's (who works for the client) regular work

ASSIGNMENT SUBMITTING STANDARDS FOR HARD COPIES

  1. All assignments are due at the beginning of the class period.
  2. Late assignments will NOT be accepted.
  3. All assignments should include the cover letter statement (click for sample) as the first page of the document.
  4. Unless otherwise stated, all printed documents should be single spaced, with 1 inch margins, and times new roman 11 font size.
  5. Systems Recommendation (SR) reports should have spiral binding (see details below). On the inside of the back cover of your document, attach an envelop that will contain single CD which contains all the submitted documents in an electronic format.

There will not be re-grading of your deliverables.

PROJECT DELIVERABLES

1. TEAM COMPOSITION (TC)

The MIS 160 teams will consist of 5 team members assigned one of the following roles:

  • Project Manager/Lead Systems Analyst
  • Database Developer/Administrator
  • Web Developer/Lead Programmer
  • Web Developer/Programmer
  • Network Designer/Administrator/Integrator

You will form groups in class on the specified date. I will provide you with the paper forms and you must complete the names of the group members, phone numbers, class schedules, work schedules, and roles. You must also include the agreed upon weekly team meeting times. 

NOTE: Because you have a primary role, it does not mean that you will not be involved in activities outside your primary role. You will be involved in all project activities but you are expected to lead in the activities within your primary role.

Other

In addition to the primary role, each developer must also assume a supporting role

Deliverables 

  1. An e-mail from the project manager with all the team member names, phone numbers, and e-mail addresses
  2. Each team member's resume attached to the e-mail

Grading 

Note that this deliverable will not be graded.

2. PROJECT SCHEDULE (PS) - 20 points

Use the MS Project software to create this deliverable. 

From the description of the project deliverables described in this document, create a project Gantt Chart to:

  • Include all deliverables described in this document (i.e., PS, SP) as summary activities.
    • Beginning day for summary activities is the day after the previous deliverable is due. Ending day for summary activities is the deliverable due date.
    • Include all tasks within each summary activity. Should, at least, include all tasks that have deliverables.
  • For each task in the Gantt chart provide name of the developers responsible (2 developers should be assigned the same task who will work together for the completion of the task) and the estimated time to complete this task.
  • Each deliverable is a milestone. You may include your own milestones.
  • Create a network diagram for your project.

Deliverable 

E-mail me a softcopy of your project file. Note that I will give you an initial grade for this deliverable. After the end of the semester you will submit the updated project file when you will receive the remaining PS points.

Grading 

2.1 Gantt Chart 10
2.2 Resource Allocation 5
2.3 Network Diagram 5

3. SYSTEM PROPOSAL (SP) - 30 points

In this deliverable you will provide documentation related to the business analysis activities of your project.

Deliverable

Service Request

  1. Name of Client Company or Organization, address, line of business, company contact, contact's phone number, and contact's e-mail address
  2. A description of how the project was initiated (provide the name of the project initiator)
  3. A brief description of the problem/opportunity to be investigated
  4. Anticipated business benefits
  5. System capabilities
  6. Indication of company size, geographical locations
  7. Personnel (by type)
  8. An organization chart for the part of the organization you are studying
  9. Business transaction types and monthly volumes

Objectives

  1. Statement of the mission/goal of the organization
  2. Define 2-3 clear and measurable objectives for your proposed system (must support the mission/goal of the organization)

Feasibility Study

  1. Technical Feasibility
  2. Economic Feasibility (MIS160EconomicAnalysis.xls)
  3. Operational Feasibility
  4. Schedule Feasibility

Note: When I review your proposal, I may require that you modify and resubmit it.

Grading 

3.1 Project Scope (SR 1-5) 10
3.2 Company Information (SR 6-9) 2
3.3 Objectives 5
3.4 Technical Feasibility 2
3.5 Operational Feasibility 2
3.6 Schedule Feasibility 2
3.7 Economic Feasibility 7

4. BUSINESS ANALYSIS (BA) - 40 points

In this deliverable you will provide documentation related to the business analysis activities of your project.

Deliverable (submit 1 copy) 

Business Analysis (BA) reports should have spiral binding and should include the items below:

Conduct of Analysis

  1. Analysis methods used
  2. End-users contacted
  3. Records, forms and reports analyzed
  4. Processes observed
  5. Problems encountered with data collection
  6. Data collection instruments
  7. Synopsis of interviews

User Requirements

  1. Customer expectations and requirements
  2. Output requirements (specify type, layout, and frequency)
  3. User training requirements
  4. System Constraints (skills, technology, etc)
  5. Business Constraints (time, funds, external factor constraints, etc)

Infrastructure Analysis

  1. Hardware
  2. Software
  3. Networking
  4. Standards

Grading 

4.1 Conduct of Analysis 10
4.2 User Requirements 20
4.3 Infrastructure Analysis 10

5. SYSTEMS ANALYSIS (SA) - 45 points

In this deliverable you will provide documentation related to the systems analysis activities of your project.

Deliverable (submit 1 copy)

Systems Analysis (SA) reports should have spiral binding and should include the items below:

UML Diagrams of the Existing System

  1. One Use Case Diagram which will show all processes
  2. Detailed description of each use case in the Use Case Diagram
  3. For each use case in the Use Case Diagram, create an Activity Diagram 
  4. Provide a list of the processing volumes/times for each activity in the Activity Diagram

UML Diagrams of the Proposed System

  1. One Use Case Diagram which will show all processes
  2. Detailed description of each use case in the Use Case Diagram
  3. For each use case in the Use Case Diagram, create an Activity Diagram
  4. Design Level Class Diagrams
  5. Design Level Sequence Diagrams 

Grading 

5.1 Use Cases of Existing System 5
5.2 Activity Diagrams of Existing System 5
5.3 Use Cases of Proposed System and their descriptions 10
5.4 Activity Diagrams of Proposed System  5
5.5 Class Diagrams 15
5.6 Sequence Diagrams 5

6. SYSTEM PROTOTYPE & INTERFACE (SPI) - 30 points

Prototype and Interface Design

Build a working prototype of your system which will serve as the proof-of-concept. The prototype must include:

  1. A MySQL database to store the data defined in your UML diagrams
  2. The main GUI Interface
  3. All sub-menus/interfaces needed by your system
  4. One form (form should update one or more tables in your database)
  5. One report generated by your system (soft or hard copy)
  6. Installation and use instructions

Grading 

6.1 Prototype GUI Interface 10
6.2 Prototype Database 10
6.3 Prototype Report 5
6.4 Installation and Use Instructions 5

7. SYSTEM RECOMMENDATION (SR) - 35 points

This document is addressed to your client and summarizes all your findings (includes all prior deliverables) and your recommendations. 

Systems Recommendation (SR) reports should have spiral binding (see details below). On the inside of the back cover of your document, attach an envelop that will contain single CD which contains all the submitted documents in an electronic format.

Deliverable

  1. Transmittal Letter addressed to your client and includes your findings
  2. Executive Summary that includes:
    • Description of problems
    • The proposed solution
    • Summary of cost/benefit analysis of the proposed solution
    • Implementation time frame of proposed solution (reference the Project Schedule as Appendix D)
    • Outline of Systems Study
  3. Detailed Results of Analysis (references corrected/updated Systems Proposal as Appendix A, corrected/updated Business Analysis document as Appendix B and corrected/updated Systems Analysis Document as Appendix C)
  4. Systems Alternatives (at least three different configurations)
    • Design Architecture
    • Hardware
    • Software (all other types of software alternatives used to implement your system)
    • Networking
  5. Systems Analystsí Recommendations 
    • Describe and support the recommended solution)
    • Provide only an updated Present Value model. You must show all cost and benefits in detail. Assume 8% rate. Create graphs for the economic analyses data. Use the NPV worksheet provided above.
  6. Proposal Summary

    PowerPoint Presentation Guidelines

    Each team will make a short (10 to 12 minutes) project presentation as shown on the syllabus schedule. Each presentation must provide the following:
    1. Description of the problem
    2. Proposed solution
    3. Systems Analysts' Recommendations
    4. Demonstration of the prototype
    5. Printed output of the PowerPoint presentation (Handouts - 3 slides per page) 
    6. At least three (3) team members must actively participate in the presentation and all other non-active team members must be available for questions

Grading 

7.1 Transmittal Letter 3
7.2 Executive Summary 5
7.3 Detailed Results of Analysis 5
7.4 System Alternatives 5
7.5 Recommendations 5
7.6 Proposal Summary 2
7.7 Presentation 10

PEER EVALUATION

In the MIS workplace, you will be asked to evaluate your subordinates, your peers, and even your managers. In this class you must complete the peer evaluation forms provided below.

../PeerEvaluationForm.xls

I will average the Percent Contribution over all forms submitted for each team member. This average will be used to allocate project points for that team member. For example, if the team members feel an individual contributed 80% towards the team project (all deliverables), then that individual will receive 80% times the total team points awarded for the semester. If a team member fails to evaluate one or more of his/her peers, it will be assumed that the contribution was 100%.

GENERAL DOCUMENTS

System Change Request is a document (I will provide Word template to each group) with the purpose to record and control all System Change Requests allowing the project team to improve the system. You must complete a System Change Request for each change to your system design that was made after you submitted the deliverable. 

ADVICE FOR A SUCCESSFUL PROJECT

  • Try to obtain a client that has a manual process that your team may automate. 
  • The proposed automated system should be designed for a PC rather than a mainframe. 
  • The sooner you can complete the information-gathering phase of the analysis, the more time you will have to devote to the design phases of the project. 
  • Try not to spend an excess amount of time on the diagrams. 
  • Realize that doing everything, as a whole team is often slow and inefficient. Use whole-team meetings primarily for brainstorming and coordinating sessions. Break the team up into smaller units, and delegate specific tasks to each of these units. These smaller units of one or two members are more efficient in completing the project "milestones" than trying to do it as the whole team. 
  • One member should be designated as "quality control" person. She/he should scrutinize the  specifications for completeness. She/he should also check narrative pages using spell check and a grammar package (e.g., Grammartique).