Vous êtes sur la page 1sur 16

School of Technology

SYSTEMS ANALYSIS WORKBOOK

Student Name: Muhammad Qasim


Lecturer: Muhammad Hassan

Term: January 2014


Group: 18B
Date of Submission: 1st May 2014

Student ID: P1019078

TASK 1
The systems development life cycle (SDLC) is a theoretical structure performed in project
management that explains the sections included in an information system development
project which includes initial project structure layout diagram to its deployment and
maintenance. System development life cycle step can be individually classified into smaller
processes. Each stage tails a logic after the previous, but it is not necessary that one stage
perform the same tail after another. It is mandatory to comprehend that system lifecycle is
iterative as well as the stage tagged along the way. It is divided into four stages.
System Development Life Cycle

Planning

Analysis

The Function & Purpose of Stage


1: Planning

The Function & Purpose of Stage


2: Analysis

The Function & Purpose of Stage


3: Design

The Function & Purpose of Stage


4: Implementation

Design

Implementation

During the phase of planning, the requirement of the


project is gathered and the objective of the product is
considered. An estimated cost and resource is
decided on the bases of the delivery date. Then all
the requirements are analyzed in order to see if an
alternative solution is available, in case of no
alternative option then requirements are reported to
the management for approval and discussion.
The analyst understand criteria and requirement of
the software and functionalities which are necessary
for the system. The analyst consider each and every
aspect in order to understand the requirements and
tries to understand the performance of system which
needs to be developed. He also make sure to collect
enough resources from the staff and provided data
to develop the required system.
In the design module number of designs of the
system are made on paper or on computer, made
sure that the design covers all the requirements of
the system. Eventually with the help of the
management the best design is being selected for
the development of the system.
This is the final phase in which the system is being
handed over to the customer so that it can be tested
in the real environment and on the actual data.

THREE of the most widely used Life Cycles + Development Methodologies


Life Cycle
Advantages
Disadvantages
Development
Methodology
Waterfall model The advantages of The disadvantage of

waterfall
development is that
is allows the team to
set
deadline,
for
example
management can set
the
date
while
programmers
can
work in the given
deadline according to
the
requirement.
Hence the complete
process can develop
like a car.

Linear
waterfall
development is that
it does not allow
flexibility or revision
in
it
process.
Eventually
if
the
application
is
in
testing mode then it
won't be possible to
change
some
functions that was
not
mentioned
previously by the
client in the concept
stage.

Life Cycle

Advantages

Disadvantages

Spiral model

The advantages of spiral


model is that, budget
issues can be sorted
much easier as more
realistic work progresses
as major issues can be
notify easily. Changes can
easily be done due to its
flexible flow

The disadvantages of this


process is that although prototyping
its
has
a
highly
customized but limited
reusability. It needs to be
apply differently for every
process. Since changes
can be made in any stage
means it has a high risk of
not meeting budget or
deadline

Life Cycle

Advantages

Disadvantages

Agile model

It is much faster than the


conventional linear model.
It gives the customer
space to give its feedback.
Development team and
customer can interact at
any stage.

It is difficult to manage
bigger projects. And
budget and deadline can
create problems.

Development
Methodology

Development
Methodology
Extreme
Programming

For the given CASE STUDY My Choice of SDLC + Methodology


SDLC: Short Time Schedule
Methodology: RAD Methodology
Reasons for my choice are;
1. The actual purpose of those modules are to speed up the development process.
2. The better choice will be to set up an appropriate time which has been given by both
development and cliental which is exactly been done in it.

3. projects can be modified or fixed if it is lacking in any phase

4. Waterfall based mythologies will never be appropriate for any projects because of its
inflexible policy

TASK 2
The REASONS for accurately capturing the functional requirements of a software
system are;
1.Giving actual requirement to the developers

2. Meet the deadline if the design is made correctly

3. Client satisfaction

4. Software success

The STRATEGIES proposed for capturing the functional requirements of the


system detailed in the CASE STUDY are;
Reading: This is one of the strategies which will help user to get the technical
requirement of application. Using this strategy user can gain full knowledge of the
company. By reading all the external reading material user can have a better
understand of the system.
Interviewing: By have a one to one interview with the customer vender can clarify all
the doubts he have in his mind regarding the system. The possible way will be that you
will meet with people or group of people face to face and will have questions prepared
for it.
Observing: By going on client place you can observe all the activity which is being
done to do the work without disturbing the staff. It will be a perfect example of common
sense.
Questioning: Another way will be to have one to one question regarding the business.
This will give you a limited but specific information depending on the questions.

TASK 3
System Modelling

Object Oriented Development

Activity Diagram - SAMPLE

Insert Card

Enter Password

Password not
accepted

Password
accepted
Select type of
transaction

Perform Transaction

More
Transaction

No more
transaction
End transaction

Activity Diagram CASE STUDY

User
Fill up form

Submit
form

Already
Registered

Librari
an

Not Registered
Verify
information
provider

Incorrect
information

Correct
Info
Create new
account

Issue ID
card

Use Case Diagram Sample


Check in book

Actor book
record

Librar
y
Patron Check out book
Actor patron
record

Pay Fine

Librarian
Add book

Report stolen

New Membership
System
boundary
Cancel
Membership

Use Case Diagram Case Study


Request
Payment
Register
Vender

Request book for


vendor

Support
IssueBooks
a book
Login
Librarian
Search a book

General
Update record
User

User
Request for
issue

Maintain
record
Unregistered
Track
complains

Registere
d user

Class Diagram - SAMPLE

Person

Passenger
0*

AAA

Driver

0..
1
Engine

1
1

Car

1
4
Tire

Class Diagram CASE STUDY

Library
-

Books database

Locations
Liberian ID

Title
Author
Book id

+ Updates ()

User

Liberian
-

Details
Liberian ID

+
+
+
+

+ Issue status ()
+ Complaints
resolution ()
+ Tracking ()
+ Calculate fine ()
+ Vender request ()
+ Payments ()

General
User
+

Sequence Diagram SAMPLE

Details
User id

Search ()
Request ()
Complain ()
Pay fine ()

Vendor
-

Book details

+ Search Books
+ Supply Books
+ Payment
details

Registered
User
+ Login ()
+ History ()
+
Unregistered

Supplier

Buyer

Get quote

Quote response
Invalid response

Sequence Diagram CASE STUDY


User

Library
Computer
1: login
1.1.1.1: Logged in or
wrong pw
2: enter book name
2.1.1.1: book found or
not
3: request for issue
3.2: book issued

Books
Database

1:1
authentication
1.1.1: acknowledge

2.1: Search for book


2.1.1: acknowledge of the

3.1: book status


issued

4: logged out
4.1: logged out
successfully
Data Flow Diagram - SAMPLE

Time Keeping
Time cards

Payroll System

Pay checks
Employees

Data Flow Diagram CASE STUDY


Book detail list

Library
Members

Library
Management
System

Student
membership
list

Teacher
membership
list

Books

Entity Relationship Diagram - Sample


See/seen by

Fine bill report

Patients

Patients

See/seen by

Treated in/home

Patients
Associated

Patients

Entity Relationship Diagram Case Study

Book id

Tag

1
Author

Has

Tags

Books
Has

Rank

Comments

Time

Link
ID

User
Text

TASK 4 (Optional)
The Analysis and Evaluation of my Proposed System Design is detailed below:

References Use Harvard Referencing

Tutorialpoint.com - Software Development Life Cycle


Available at: http://www.tutorialspoint.com/sdlc/sdlc_tutorial.pdf

onestopqa.com - SDLC Models


Available at: http://www.onestopqa.com/resources/SDLC%20Models.pdf