An Abuja based 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.
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 N500000. 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 system scope document attached with this assignment. Here are some things to consider:

Your Use Case Diagram must have at least three meaningful processes

Your project must result a new business improvement design in one of the following
forms:
o Automated replacement of current manual system design
o Substantial redesign of an existing automated system
o New automated design to be placed on existing automated system

I permit students to work on a project for their employer under the following
assumptions:
o The entire group supports this project
o 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
o The student that works for the client, will not be the primary contact with that
client

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 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.

o This project is not part of the student's (who works for the client) regular work
Systems Recommendation (SR) reports should have spiral binding (see details below). On the
inside of the back cover of your document, attach an envelope that will contain single CD which
contains all the submitted documents in an electronic format.
ASSIGNMENT SUBMITTING STANDARDS FOR HARD COPIES
1. All assignments are due at June 30th 2015.
2. Late assignments will NOT be accepted.
3. All assignments should include the cover letter 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.

PROJECT DELIVERABLES
1. TEAM COMPOSITION (TC)
The teams will consist of 3 team members assigned one of the following roles:

Project Manager

Lead Systems Analyst

Business Analyst

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.
o Beginning day for summary activities is the day after the previous deliverable is
due. Ending day for summary activities is the deliverable due date.
o 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 team member responsible. Each
deliverable is a milestone. You may include your own milestones.

Create a network diagram for your project.

Grading
2.1 Gantt Chart

10

2.2 Resource Allocation

2.3 Network Diagram

3. FEASIBILITY STUDY REPORT (FSR) - 20 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. Business drivers: Describe the reasons for starting this project (problem and/or
opportunity and/or mandate)
4. Anticipated business benefits
5. System capabilities
6. Indication of company size, geographical locations
7. An organization chart for the part of the organization you are studying and personnel (by
type)
8. Business transaction types and monthly volumes
Goals and Objectives
1. Statement of the mission of the organization
2. Organizational goals
3. Define at least 3 clear and measurable SMART business (not system) objectives for your
proposed system (must support the mission/goal of the organization)
Feasibility Study
1. Technical Feasibility
2. Economic Feasibility (see example of economic feasibility report)
3. Operational Feasibility
4. Schedule Feasibility
Note: When I review your proposal, I may require that you modify and resubmit it.

Grading
3.1 Service Request

3.2 Mission and goals

3.3 Objectives

3.4 Technical Feasibility

3.5 Operational Feasibility

3.6 Schedule Feasibility

3.7 Economic Feasibility

4. BUSINESS ANALYSIS (BA) - 30 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
Software Requirements Specification (SRS)
1. External Interfaces
2. Functions
3. Usability Requirements
4. Performance Requirements
5. Logical Database Requirements
6. Design Constraints
7. Software System Attributes
Infrastructure Analysis

1. Hardware
2. Software
3. Networking
4. Standards
Grading
4.1 Conduct of Analysis

4.2 User Requirements

15

4.3 Infrastructure Analysis

10

Reading Recommendations:
1. Systems and software engineering Life cycle processes Requirements engineering
(ISO/IEC/ IEEE 29148)
2. IEEE Recommended Practice for Software Requirements Specifications (IEEE Std 8301998)
5. SYSTEMS ANALYSIS (SA) - 20 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. Use Case Diagram(s) 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. Case Diagram(s) 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. Domain Model Class Diagrams
5. System Sequence Diagrams
Grading
5.1 Use Cases of Existing System

5.2 Activity Diagrams of Existing System

5.3

Use Cases of Proposed System and their

descriptions

5.4 Activity Diagrams of Proposed System

5.5 Sequence Diagrams

6. SYSTEM RECOMMENDATION (SR) - 20 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:
o Description of problems
o The proposed solution
o Summary of cost/benefit analysis of the proposed solution
o Implementation time frame of proposed solution (reference the Project Schedule
as Appendix D)
o 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)
o Design Architecture
o Hardware
o Software (all other types of software alternatives used to implement your system)
o Networking
5. Systems Analysts Recommendations
o Describe and support the recommended solution)
o 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.

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:
o Description of the problem
o Proposed solution
o Systems Analysts' Recommendations
o Printed output of the PowerPoint presentation (Handouts - 3 slides per page)
o All (3) team members must actively participate in the presentation and must be
available for questions

Grading
7.1 Transmittal Letter

7.2 Executive Summary

7.3 Detailed Results of Analysis

7.4 System Alternatives

7.5 Recommendations

7.6 Proposal Summary

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.
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
ADVICE FOR A SUCCESSFUL PROJECT

Try to obtain a client that has a manual process that your team may automate.

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 wholeteam 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.
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%.

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).