paper
Systems Analysis Methods Project Report
Sample Only
Project Name: < Project name goes here>
Team#: < goes here>
Team Members:
< member names>
Version:
1. Introduction
1.1. Systems Objectives
<Describe briefly the purpose of the project.>
Sample:
The main objectives of this project are to:
· streamline the operation of the current library system.
· enhance the system architecture and the interoperability …
1.2. Background
<Describe the business-related reason for initiating the project and the system requests to solve the problem or to achieve any objective according to the business needs of stakeholders.>
Sample:
In the Government, library management functions are mostly practiced in manual ways with the aid of various computer systems. For those libraries that implemented individual systems to streamline their workflow, the systems are typically used for keeping records ...
1.2.1 Current System Description
<Include brief description of the current systems information.>
Sample:
The current system allows Users to borrow books, who must first manually search if there are any available stocks. The User then must display their library card to a Librarian, who will then issue the book…
Figure 1 Current System
1.3 Proposed System
<Describe the basic information of proposed system functions which can deliver value to the business needs according to the collected system requirements.>
2. Project Overview
Sample:
The proposed IT system will enable Users to sign into the library system using their mobile application, and where they can search for their desired book and immediately see if there is any stock available. If the book is available and not reserved, and the User has no outstanding fines, the librarian will issue the book to the User…
Figure 2 Use case diagram for the proposed system
2.1. System Functions
Sample:
The proposed system will cover the following major function areas:
Table 1 System Functions
|
Item |
System Functions |
|
1 |
Common requirements for Library Management System |
|
1.1 |
The general functional requirements for features in the Library System which includes... |
|
2 |
Book Management System |
|
2.1 |
Book record maintenance |
|
2.2 |
House Keeping |
|
3 |
Borrow Book System |
|
3.1 |
… |
2.2. Resource Implications
<Describe the resource required including effort in terms of person-days or cost.>
Sample:
The estimated staff resources required in person-days to develop the system and to provide ongoing system maintenance are summarized below:
|
Stage/Role |
Program Manager (student names: ) |
Business Analyst (student names:) |
System Analyst (student names: ) |
Analyst Programmer, if any (student names: ) |
Any other (student names: ) |
|
Stage 2 – Systems analysis |
30 |
60 |
80 |
120 |
30 |
|
Stage 3 – Proposal |
10 |
30 |
60 |
30 |
10 |
|
Stage 4 - Diagrams |
10 |
10 |
30 |
60 |
0 |
|
Stage 5 – Presentations |
20 |
20 |
80 |
80 |
0 |
|
Stage 6 – Final Report |
5 |
0 |
10 |
10 |
0 |
|
Stage 7 – … |
5 |
... |
… |
… |
… |
|
Total |
80 |
… |
… |
… |
… |
2.3. Costs, Marketing, and/or Benefits Analysis
2.3.1. Costs
<List the non-recurrent cost and annual recurrent cost of the project including the staff effort and hardware/software/service required.>
Sample:
For implementation of the Library Management System, the estimated total non-recurrent and annual recurrent costs are $11,880,000 and $1,798,000 respectively.
|
Non-Recurrent Cost |
Cost (US Dollars) |
|
Hardware & Software |
$2,000 |
|
Service implementation |
$1,000 |
|
IT-Staff |
$5,000 |
|
Total |
$8,000 |
|
Annual Recurrent Cost |
Cost (US Dollars) |
|
Hardware & Software |
$400 |
|
Service implementation |
$500 |
|
IT-Staff |
$1,000 |
|
Total |
$1,900 |
2.3.2 Benefits
<Describe the business value of the system which can benefit the organization.>
Tangible Benefits
The system is contributed to achieving the following benefits:
Library Management System helps the library lower the cost of daily operation and services.
With Library Management System, there is no need to acquire servers and equipment for individual installation and hence the maintenance costs of hardware can be greatly reduced.
Library can adopt the system by contributing one-off adoption cost for…
…
Moreover, each library can subscribe the desired function modules as required and …
Intangible Benefits
Library Management System will adopt the cloud technology and service-oriented architecture which allow the data/system functions to be conveniently shared across different libraries. In this way, the deployment lead-time is largely improved and benefits can be realized more quickly...
2.3.3 Project Plan <List the work plan for the project according to the selected development approach, time frame and estimated effort required.>
Sample:
The production launch of Library Management System will take place in May 2019. The major activities are tabulated in the following table:
|
Items |
Activity |
Start Date |
End Date |
|
2 |
Business Process Re-engineering Study |
Jan 2019 |
Jan 2019 |
|
3 |
System Analysis and Design |
Feb 2019 |
Mar 2019 |
|
4 |
Porotype Development |
Jan 2019 |
Mar 2019 |
|
6 |
User Acceptance Test |
Mar 2019 |
Apr 2019 |
|
9 |
System Documentation |
Jan 2016 |
Apr 2019 |
|
… |
… |
… |
… |
|
… |
Proposal Presentation |
||
|
… |
Presentations |
Feb 2016 |
Apr 2019 |
3. Current App/System Overview
<Include a high-level diagram showing the interactions between the system and the user, as well as any interfaces or interactions between the system and external systems/parties.>
<Diagram for high level system overview.>
Sample:
Figure 3 High-level system diagram
High level system overview:
|
Subsystem |
Function |
|
<List the subsystems> |
<List the functions> |
|
Library system |
- Borrow - Renew - Return
|
3.1. Current Business Process
<Include the model of current business process and follow by a table/paragraph to elaborate the process if needed. Typically, the major elements that need to be captured in the Process Diagrams are:
Event
· Denote something that happens
Activity
· Describe the kind of work that needs to be performed
Gateway
· Describe the decision factors and determines where the next step should go
Connections
· Describe how the process flow objects are connected.>
<User type as well as the system / process boundary can also be included in a swim lane diagram. A complex business process can be broken down into sub-level if needed.>
<Business process diagram(s).>
Sample:
Figure 4 Business Process Diagram
3.2. Current Problems and Issues
<Provide the problems and issues encountered by the business or IT currently.>
Problems and issues:
|
No. |
Description |
|
<Unique number> |
<Description> |
|
1 |
User must be able to display their Library Member Card to Librarian before having the book issued to them. |
|
2 |
Current system does not support e-book… |
4. Systems Analysis
4.1. Proposed System Overview
<This section provides a brief description about the proposed IT system to be developed by presenting a high-level conceptual model of the system and showing a system user profile about the users of the proposed IT system that will be referred to in following sections.>
Sample:
The proposed IT system will enable Users to sign into the library system using their mobile application, and where they can search for their desired book and immediately see if there is any stock available. If the book is available and not reserved, and the User has no outstanding fines, the librarian will issue the book to the User…
Figure 5 Use Case Diagram of the proposed system/app
4.1.2. … diagrams
<Include a diagram to show the components of each subsystems.>
<Class Diagram(s).> Also include a short description of each diagram.
Sample:
Figure 6 Class Diagram
<Include diagrams such as a sequence or activity diagram to identify the internal flow of control between components.> Also include a short description of each diagram.
<Sequence Diagram(s).>
Sample:
Figure 7 Sequence Diagram
<Activity Diagram(s).>
Figure 8 Activity Diagram
<Include diagrams such as state diagram to describe the behavior of a single object in response to a series of events in a system.> Also include a short description of each diagram.
<State Diagram(s).>
Figure 9 State Diagram
4.1.3. User Experience Design
<Include the UI information architecture such as a site map to provide a top-down view of how the users will interact with various pages, functions, and content and identify the screens or pages that would be developed for the application and their relations.>
<UI information architecture.>
Figure 10 UI Information Architecture
<For each mock-up, include the picture of the mock-up, and describe the elements presented within the mock-ups, screen actions and messages if applicable.>
<Picture of mock-up.>
Sample:
Elements presented (if applicable):
|
Field Name in Mock-up |
Table Name, Column Name |
Data Type |
Validation |
Comments |
|
<Input> |
<Input> |
<Input> |
<Input> |
<Input> |
|
Keyword |
N/A |
Text |
No special characters |
N/A |
Screen actions (if applicable):
|
Type |
Label |
Action |
Comments |
|
<Input> |
<Input> |
<Input> |
<Input> |
|
Button |
Search |
Search the database for matching book titles |
N/A |
Messages (if applicable):
|
Message ID |
Description |
Type |
Triggering Event |
|
<Input> |
<Input> |
<Input> |
<Input> |
|
Error1 |
Display warning when no keyword is entered |
Warning |
Search |
5. Conclusions
Summarize the information about the system design and potential benefits.