[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 1

Contents
1.0 Project Planning ...................................................................................................................................... 3
1.1 Introduction ......................................................................................................................................... 3
1.1.1 Aims ............................................................................................................................................. 3
1.1.2 Objective ...................................................................................................................................... 3
1.2 Problem analysis ................................................................................................................................. 4
1.3 Proposed Solution ............................................................................................................................... 4
1.4 Scheduling........................................................................................................................................... 5
1.4.1 Timeline ....................................................................................................................................... 5
1.4.2 Work ............................................................................................................................................ 6
2.0 System Analysis ...................................................................................................................................... 7
2.1 Requirement Elicitation ...................................................................................................................... 7
2.1.1Interview ....................................................................................................................................... 7
2.1.2 Questionnaire ............................................................................................................................... 9
2.1.3 Conclusion ................................................................................................................................. 10
2.2 Methodologies................................................................................................................................... 11
2.2.1 SDLC ......................................................................................................................................... 11
2.2.2 Waterfall Model ......................................................................................................................... 13
2.2.3 JAD ............................................................................................................................................ 16
2.3 Selection of Methodology ................................................................................................................. 18
2.4 Feasibility Studies ............................................................................................................................. 19
2.4.1 Feasibility Study ........................................................................................................................ 19
2.4.2 Economic Feasibility.................................................................................................................. 20
2.4.3 Operational Feasibility ............................................................................................................... 21
3.0 Logical Design ...................................................................................................................................... 22
3.1 Conceptual Design ............................................................................................................................ 22
3.2 Process Design .................................................................................................................................. 23
3.2.1 Level 0 Diagram......................................................................................................................... 23
3.2.2 Level 1Diagram.......................................................................................................................... 24
3.3 Data Design ....................................................................................................................................... 25
[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 2

3.4 Behavior Design ................................................................................................................................ 26
3.4.1 State Diagram ............................................................................................................................. 26
4.0 Physical Design ..................................................................................................................................... 27
5.0 Selection of Methodology ..................................................................................................................... 33
5.1 Waterfall Model (Khaled Gamal Individual Part) TP023701 ........................................................... 33
5.2 RAD & SSADM (Eissa Sawadi Individual Part) TP029141 ............................................................ 38
6.0 Reference .............................................................................................................................................. 47



















[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 3

1.0 Project Planning

1.1 Introduction
Availability of books and reading materials for purchase in (APU) is quite inadequate. Although
the APU library have large collection of books (both hard copy and e-books), this project is for
developing an APUs E-Bookstore to establish an e-bookstore. Online shopping will purchase
the latest books and supplies many genres.

1.1.1 Aims
The purpose of analysis and design is to show how the system can be realized. The goal is to
create a system that:
Performs in a particular environment, the objectives and functions set forth in the
description of use case.
Performs all its requirements.
Easily change when functional requirements change.
The design results in model design and analysis of optional analysis model. The design model is
an abstraction of the source code, i.e., the design model acts as a "blueprint" as the source code is
structured and written. The design model consists of design classes structured into packages and
subsystems with well-defined interfaces, representing what will become components in the
implementation. It also contains a description of how these classes of design objects cooperate to
perform the use cases.

1.1.2 Objective
The project will cover the Structured Systems Analysis Design Method methodology
selection and justification, analysis. Accordingly, process, data modeling, data dictionary,
context and data flow diagram.
Improve control and management development.
Develop a better quality system.
The project will be able to support through a computer-based tool.
Increase efficiency by reducing human errors, reducing wasted time searching for
documents.
Reduce costs by eliminating inefficient paper system.

[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 4

1.2 Problem analysis
Currently the student population of APU e-bookstore has increased. Although the APU library
has a large collection of books (both printed and electronic books), presence, and it is very
limited due to many limitations. Student and Staff only options are a small bookstore within the
enterprise. Increased book store in the university often sorted for the other varieties.
Through their current system, the university objectives become difficult to be achieved and this
may lead the university not to be able to meet their students satisfaction and expectation at their
level of services that being conducted.
The existing book records within the university are being recorded into traditional files; this
affects the university especially due to the increasingly number of books into different
departments. Hence, it makes both the administration difficult to track the university books
information according to their designation and departments they are working. Also may results
into time-consuming process to generate book reports that should be used by the university
administration.

1.3 Proposed Solution
With the increasing population in the APU, the university plans to create an e-bookstore. The
online store is the purchase of latest books and material of many genres.
One of the most important advantages of this system is to provide an online store. The database
associated with the university web site and when an administrator to add books to the database,
students and teachers will be able to access the database after logging in and buy or check the
book.
The system is more secure. For another account different privileges defined in the system. The
administrator at the university can access all the information in the database, and he / she is able
to edit, modify and download books in the database.
Although the system fulfills the requirements of all university system is designed in a very user-
friendly and easy way. The administrator can easily load data into the system, as well as students
and teachers can view information very easy. The graphical interface makes the system even
easier.




[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 5

1.4 Scheduling

1.4.1 Timeline

Days 1-5 6-12 13-25 26-40 40-45 46-47 48
Tasks
Project Planning
System Analysis
Logical Design
Physical Design
Methodology
Assignment
Compilation

Assignment Completion






[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 6

1.4.2 Work
























Components Khaled Gamal
(TP023701)
Eissa Sawadi
(TP029141)
Project Planning


System Analysis


Logical Design

Physical Design

Select of Methodology

Documantation

[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 7

2.0 System Analysis
Analysis is when you say to prove your results or disprove assumptions or hypotheses. Explain
why your results were like this. Analysis is the process in which the whole into parts. Work
analysis is the process used to collect information about the duties, responsibilities, necessary
skills, outcomes and conditions of the specific job. You need as much data as possible to the
often gather the job description, the result of the analysis. Additional results include a number of
plans, position reports and advertising, and the effectiveness of development planning in your
performance management system.

2.1 Requirement Elicitation
Fact-finding is the formal process of using interviews, questionnaires, research, meetings, and
observation about system problems, requirements and preferences to collect. It is also called
information gathering or data collection. The questionnaires and interviews technique is selected
for the APU e-bookstore.

2.1.1Interview
Interviewing is a fact of equipment by system analysts gathers information from individuals from
across face-to- face interaction. If we are to successfully interviewed first, choose people to
interview. Thus, the caller must ensure that all the key people in the study boundaries are. Next
find the right way to conduct personal interviews. Thus, the good interpersonal relationships
should be considered and the interviewer must establish some connection with someone to make
cooperation necessary to get all the relevant facts." (IT Hawryszkiewycz, 1994)
Interviews were organized and conducted with a prepared questionnaire to provide a better
solution for e- bookstore requirements SCU using smart technology. Below is an example of the
interview:







[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 8

Interview with the manager
Is there any online service been rendered at this moment?
At present, there is no online service which students can use to purchase the book in online, but
there are plans on the way for an online service, hopefully soon.
Is there any service charge? If yes, then how much is it?
No.
What are the terms of payment? Cash or through ATM
We only accept payment by online.
What is the main information you require from your students?
The most important information we need from our students are students name which is the most
important, students address which gives his/her location, students telephone number. Other
information apart from these is considered secondary.

Interview a few students
How do you rate the current trend of APU's e-bookstore?
I would say that their services are better compared to other universities in this kind of business. I
think I can give them a pass mark.
How do you rate their website services?
Excellent
Do you think they need improvement or the trend is ok as it is now?
Definitely yes, their technology has to be improved; maybe they should computerize all their
system. I am not condemning the present state, but if they really want to get to that stage of been
a household name.
What do you know about the APU's e-bookstore?
APU's e-bookstore library has large collection of books (both hard copy and e-books). The
students can buy the book from the website.

[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 9

2.1.2 Questionnaire
Questionnaires offer a special document that allows the analyst to collect information and
opinions of a large number of respondents. It is suitable for the facts of our technique because it
is elastic and the measurement data types. In addition, it measures both qualitative and
quantitative data to get accurate results and saves time. Therefore, the questionnaire carefully
design and implement in society. Below is an example of the questionnaire:
Please feel free to complete our feedback questionnaire.

Name: _____________________________
Address : _____________________________
Telephone: _____________________________
Date: _____________________________

5*
(Excell
ent)
4*
(Very
Good
)
3*
(Go
od)
2*
(Ave
rage
)
1*
(Poo
r)
What is your level of satisfaction regarding
books/information available in different section of
library


What is your satisfaction regarding available books/
journals/ information


What is the time taken in transaction the books/
journals


What is the time in transaction of the books/
journals



Is there any other service you would like us to offer you?

______________________________________________________________

Thank you for taking the time to give us your feedback.

[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 10

2.1.3 Conclusion
After analyzing the collected information, the results above can conclude that the APU's e-
bookstore system food delivery system somehow able to fulfill the publics requirements. The
APU's e-bookstore seems to have a great ability of being brought onward to another step of its
projects development. The outcome of this questionnaire has also enabled the development team
to shows that the public needs from a e-book store and how the system will be operation.
Overall, the public needs the system and the APU's e-bookstore development would be done
within the due date.




















[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 11

2.2 Methodologies

2.2.1 SDLC

Systems Development Life Cycle (TSRS) is a process used by systems analyst to develop an
information system, including requirements, testing, training, and user (stakeholder) ownership.
Any SDLC should result in higher quality systems that meet or exceed customer expectations,
reaches completion on time and no budget to work effectively in current and planned information
technology infrastructure, and inexpensive to maintain and cost effective for improvement.
(Howe, 2000)
SDLC has different phases, which are briefly described here.








[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 12

Phase Explanation
Initiation Begins when a sponsor identifies a need for an opportunity, then concept proposal is
created.
System Concept
Development
Defines the scope of boundary of the concepts, includes systems boundary documents,
cost benefit analysis, risk management plan and feasibility studies
Planning Develop Project Management Plan and other planning documents. Provides for the basic
resources needed to achieve solutions.
Requirement
Analysis
Analyses user needs and develops users requirements create a detailed functional
requirements document.
Design Transforms detailed requirement, into complete detailed systems design document
focuses on how to deliver the required functionality.
Development Converts a complete information system design includes the purchase and installation of
the environment, creating and testing databases, developing test procedures, preparation
of test files, coding, compiling, processing applications, performing test readiness review
and procurement.
Integration and
Test
Demonstrates the developed system conforms to requirements as specified in the
functional requirements document. Conducted by quality assurance staff and users.
Produces tests analysis reports
Implementation Includes implementation preparation, of the system into a production environment, and
resolutions of problems identified in the integration and test phases.
Operation and
Maintenance
Describe tasks to operate and maintain information systems in a production environment,
include post-implementation and in-process reviews
Disposition Describe end of system activities, emphasis is given to proper preparation of data








[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 13

2.2.2 Waterfall Model

Waterfall model is a sequential design process, often used in software development processes, in
which progress is seen as flowing steadily downwards (like a waterfall) through the phases of
Conception, initiation, analysis, design, manufacturing, testing and maintenance.
The waterfall development model has its roots in industry and construction, highly structured
physical environments in which after the fact of change is too costly, if not impossible. Since no
formal software development methodologies existed at the time, this device-centric model
simply adapted for software development.
Waterfall model moves from one stage to another in sequential order. For example, one of the
first completes requirements specification, which after sign -off are " set in stone ". When
requirements are completed, one proceeds to design. The software in question is designed and a
plan drawn to performers (coders) to further this design should be a plan for implementing the
requirements given. The design is completed; the implementation of this design is made coders.
In the later stages of this implementation phase, separate software components created combined
to introduce new functionality and reduce risk by removing errors.






[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 14

Phases of the waterfall model
i. Requirements analysis and definition
All possible requirements of the system are collected in this phase. The requirements are
collected from the end-user by consultation, the requirements are analyzed in terms of their
credibility and ability to include them in the system, the report specification is carried out on the
next stage of the model.
ii. System & Software Design
System design was prepared on the basis of the report. System Design helps in determining the
hardware and system requirements, and easily determines system architecture. The system
design specifications serve as input for the next stage of the model.
iii. Implementation and unit testing
From Phase II, the task is broken into pieces and the actual coding starts and each unit is checked
to see if it meets specified requirements before integration into the next phase.
iv. Integration and system testing
Integrates units in the complete system and tests for smooth coordination units within the system
and analyze if the system meets all the technical requirements set out when successfully tested
the product is delivered to the customer.
v. Operations and Maintenance
This is an on-going phase to analyze and resolve problems with the system which did not prevail
during development phases.








[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 15

Benefits
It is easy to plan and schedule the project. Helps plan and project schedule that can be set
with deadlines for each stage of the product might go through a process of development
and will be delivered on time.
Clearly defined stages. Phases and activities clearly identified where development is
moving from concept, through design, implementation, testing, installation,
troubleshooting, operation and maintenance.
Easy departmentalization and managerial control. Schedule can be set with deadlines for
each stage of the product might go through a process of development and theoretically be
delivered on time. Each phase of development proceeds in strict order, without any
overlapping or iterative steps.
It is easy to explain to the user.
Control at each stage allows time to detect errors / misunderstandings.
Disadvantages
Cost of development. When new customer requirements added to the list, it leads to re-
design the system, and can sometimes be the result of a new version of the system, thus
increasing the cost of developing the system for a short period of time.
The customer can not define requirements explicitly. It suggests requirements remain
unchanged during the project. Thus, there is little chance of incorporating new changes
when the project is started; this leads to confusion and further delays.
It is hard to go back stage. Once the program is in testing, it is very difficult to go back
and change something that was not well described in the concept stage. In general, the
project is not divided into phases flexible








[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 16

2.2.3 JAD
The use of common design (JAD) was developed by Chuck Morris IBM Raleigh and Tony
Crawford of IBM Toronto in the late 1970s. In 1980, Crawford and Morris taught JAD in
Toronto and Crawford gave several seminars for proof of concept. The results were encouraging
and JAD approach has become widely accepted in many companies. Originally JAD was
designed to bring the system developers and users of all backgrounds and opinions together in a
productive and creative environment. Meetings were way to get quality requirements and
specifications. The structured approach provides a good alternative to traditional sequential
systems analysts interview. (Yatco, 1999)

Identify project objectives
and limitations
The pre-workshop activities, planning and scoping, set
expectations of the workshop sponsors and participants.
Scoping identify business functions that are within the
project.

Identify critical success
factors
It is important to identify the critical success factors for
the development of projects and business functions are
studied.

Define project deliverables It is important to determine the form and level of detail of
the workshop documentation. results of the workshop
documentation

Define the schedule of
workshop activities
The activities which has to be done in a workshop must
be planned and scheduled

Select the participants These business users are professionals and outside
experts that will be needed for a successful seminar.

Prepare the workshop
material
The workshop material consists of documents,
spreadsheets, charts, and even props, which allows us to
understand business functions under investigation.

Organize workshop activities
and exercises
Facilitator should design workshop exercises and
activities to provide interim results, which build up the
final results of the workshop.

Prepare, inform, educate the
workshop participants
All participants must be aware of the goals and
constraints of the project and expected outcomes of the
workshop.
8







7



6
5
4
1
3
2
1
[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 17


Coordinate workshop
logistics
Workshops should be held off-site to avoid interruptions.
Projectors, screens, computers, tables, markers, masking
tape, paper for notes, and many other details need to be
prepared.

Benefits of JAD
JAD reduces the time and cost associated with the process of extraction.
JAD promotes convergence bringing them together experts to share their opinions, to
understand the views of others and develop a sense of ownership of the project.
Easy integration of CASE tools in workshops JAD sessions improves performance and
provides system analysts with discussing and ready to use model.















9
[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 18

2.3 Selection of Methodology
Structural Analysis and Design System (SSADM) is a systematic approach to analysis and
design of information systems.
Structural analysis gives a clear and understandable statement for non-technical people. In fact, it
is always difficult for technicians to describe a system of concepts back to the user in terms the
user can understand. Structured methods usually involve the use of easy to understand, non-
technical schematic methods. Importantly, these charts should not contain technical details that
the user can understand and be understood.
We used SSADM as our design method in the proposed project. SSADM is used in the analysis
and design stages of the system.
The reason why we use SSADM is that it is easy to develop. It has many advantages such as:
Three different views of the system
Mature
Separation of logical and physical aspects of the system
Well-defined techniques and documentation
User involvement
In this situation, we decided to analyze the problem and the size of the university, we decided to
use SSADM.

[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 19

2.4 Feasibility Studies

2.4.1 Feasibility Study
In order to determine whether the project is feasible or not, should be some form of investigation
objectives and outcomes of the project. For very small projects it may not be necessary at all,
since the scope of the project easily apprehended. In large projects, the opportunity can be done,
but in the informal sense, or because there is no time for formal training or because the project is
a "must have" and should be made one way or another.
When a feasibility study is carried out, there are four main areas to consider "Technical,
Financial, Organizational, and Ethical".
The feasibility study is effectively a condensed version of a fully-blown systems analysis and
design. User requirements and analyzed to some extent, several options for business and even
made some technical details of the implementation. The product of this phase is formal
document feasibility.
SSADM specifies the sections that the study should, including any provisional models that have
been built and also any options rejected and the reasons for their rejection. (MSc-IT Study
Material, 2007)












[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 20

2.4.2 Economic Feasibility







Development Cost Cost (RM)
Software license for Visual Studio 2008
Temporary Hardware for Development and Testing
Employee Training
2000
2000
1000
TOTAL

System Benefits Cost (RM)
Man power saved
Telephony Bills
Failure Cost
Net profit
4000
1000
4000
1000
TOTAL 10000










Operational Cost Cost (RM)
Software license for Database Program
Software license for Operating System
Intenet subscription fees
Employee salary for maintenance department
Employee salary for payroll system
PC and computer peripheral for every department
1000
1000
300
2000
1000
15000
TOTAL 20300
[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 21

2.4.3 Operational Feasibility
For any system, if the expected benefits equal or exceed the estimated costs, the system can be
evaluated as economically feasible. The economic feasibility, cost-benefit analysis done in which
the expected costs and benefits are evaluated. Economic analysis is used to assess the
effectiveness of the proposed system. The economic feasibility of the most important is cost-
benefit analysis. As the name implies, this analysis of the costs to be incurred in the system and
the benefits derived from the system.
2.4.3.1 Performance
For the new APU e-bookstore system, the developer uses computerized system to count the
employee salary automatically according to their statistic info. It will eliminate the need for the
manager to count the salary manually based on their statistic. Through automatic counting salary,
it will reduce mistake and eliminate delays.
2.4.3.2 I nformation
The new system should be quick to obtain the necessary information. Information associated
with the keyword when it should be able to retrieve the information. The user in short time
Database information should also be easy to update some information.
2.4.3.3 Economy
The initial cost of the new proposed system can be so expensive. But in the future it will be much
cheaper, because the return value of the investment will be very high. The reason is simple: do
not need to hire as many employees to cope with the system.
2.4.3.4 Control
A great system is to prevent password-protected and that other people have access to confidential
data. The proposed system will be extended with a good safety wall and no threat to information
or data. The data would be safe and secure.
2.4.3.5 Efficiency
The new proposed system has a much better performance compared to the current system,
because every information can be stored in a quick way, without the need to hire as many
employees to cope with everything. In addition, it will facilitate the manager to keep track of
things that occurred in the system, so it will reduce the error.
2.4.3.6 Service
The purpose of new system is to improve the quality of giving service to student, such as giving
their book on the internet and provides them every the books.



[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 22

3.0 Logical Design

3.1 Conceptual Design
A Context Diagram is a diagram showing how external entities to interact with the system shows
that send input and get output from the system. The context is also known as CD is a data flow
diagram that models the entire system, their sides being in a single process box for the system of
border. Below is the CD of the current system:


[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 23

3.2 Process Design

3.2.1 Level 0 Diagram





[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 24

3.2.2 Level 1Diagram






[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 25

3.3 Data Design
Entity Relationship Diagram (ERD) is a structure that shows the representation of the data and
the relationship between the entities. The ERD helps the system analyst with a clear view of the
relationship between the entities. Below is the ERD for the proposed system;




[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 26

3.4 Behavior Design
3.4.1 State Diagram
Online Registration and Book Selection (By Members)



[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 27

4.0 Physical Design





[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 28






[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 29





[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 30







[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 31









[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 32










[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 33

5.0 Selection of Methodology

5.1 Waterfall Model (Khaled Gamal Individual Part) TP023701
Waterfall model is a popular version of the systems development life cycle model for software
development. Often considered the classic approach to the systems development life cycle, the
waterfall model describes a development method that is linear and sequential. Waterfall
development is specific targets for each stage of development. Imagine a waterfall on steep
mountain cliffs. Once the water went over the edge of the cliff and began his journey towards the
mountain, it cannot return. It's the same with waterfall development. Once the development
phase is completed, the development will be the next step and now there is no turning back.
Waterfall model is one of the techniques that are currently used to design systems. This model
has several advantages, but also has some disadvantages. One of the benefits that are available in
this model is that the developer will take a few steps waterfall model until it progressing step to
the next step developer will ensure that every step of the waterfall are met. And one of the
drawbacks of this model is that the amendment to the part of the system is difficult.


[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 34


1. Requirement

Unless you know what you want to design, you cannot proceed with the project. Not only big projects,
but even a small code of adding two integer numbers also needs to be written with the output in mind.
Here, in this stage, the requirements which the software is going to satisfy are specified. All requirements
are presented to the team of programmers. If this phase is completed successfully, it ensures a smooth
working of the remaining waterfall model phases, as the programme is not burdened to make changes at
later stages because of changing requirements.

2. Analysis

As per the requirements, the software and hardware for the proper completion of the project is analyzed in
this phase. Right from the point of which computer language should be used for the designing of the
software, to the database system that can be used for the smooth functioning of the software is decided at
this stage.

3. Design

The algorithm or flowchart of the program or the software code to be written in the next stage is created
now. It is a very important stage, which relies on the previous two stages for its proper implementation
and the proper execution of the same ensures a smooth working of the next stage. If during the design
phase it can be made out that there are some more requirements for designing the code, it is added up to
the list in the analysis phase and the design phase is carried out according to the new set of resources.

4. Coding

Based on the algorithm or flowchart designed, the actual coding of the software is carried out. This is the
stage where the entire idea of the software of program to be designed is materialized. A proper execution
of the previous stages ensures a smooth implementation of this stage.



[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 35

5. Testing

With the coding complete, the testing department now comes into scene. It checks out if there are any
flaws in the designed software and if the software has been designed as per the specifications. A proper
execution of this stage ensures that the client, for whom the software has been designed, will be satisfied
with the work. If there are any flaws, the problem is reverted back to the design phase. In the design
phase, the changes are implemented and then its succeeding stages, coding and testing are again carried
out.

6. Acceptance

This is the last stage of the software development, using the waterfall model. A proper execution of all the
preceding stages ensures software as per the requirements and most importantly, it ensures a satisfied
client. However, at this stage you may need to provide the client with some support regarding the
software you have developed. If the client demands some further enhancements to be made to the existing
software, then the process again needs to be started, right from the first phase, i.e., requirements.


[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 36

Comparison between Waterfall Model, Spiral Model and Incremenal Model

Model Advantage Disadvantage

Waterfall
Simple and easy to use.
Easy to manage due to the
rigidity of the model each
phase has specific
deliverables and a review
process.
Phases are processed and
completed one at a time.
Works well for smaller
projects where requirements
are very well understood.
Adjusting scope during the
life cycle can kill a project.
No working software is
produced until late during
the life cycle.
High amounts of risk and
uncertainty.

Spiral
High amount of risk
analysis.
Good for large and mission-
critical projects.
Software is produced early
in the software life cycle.

Can be a costly model to
use.
Risk analysis requires
highly specific expertise.
Project's success is highly
dependent on the risk
analysis phase.
Doesn't work well for
smaller projects.

Incremental
Generates working software
quickly and early during the
software life cycle.
More flexible less costly
to change scope and
requirements.
Easier to test and debug
Each phase of an iteration is
rigid and do not overlap
each other.
Problems may arise
pertaining to system
architecture because not all
requirements are gathered
[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 37

during a smaller iteration.
Easier to manage risk
because risky pieces are
identified and handled
during its iteration.
up front for the entire
software life cycle.





















[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 38

5.2 RAD & SSADM (Eissa Sawadi Individual Part) TP029141

Introduction
In a research report, nor even in normal community is really important to plan all the activities,
or even just a simple way to ensure that the management process flow will run smoothly. To help
it, organizations need to correct approach. What methods and methods from these studies of the
benefits is it?
Systems approach, in fact, improves the management of the process, control system
development, processing, in addition to maintaining a very specific techniques and activities. It is
very important to choose the best way to organize and manage these systems in order to reduce
complications, in addition to running these events planned in the flow. Each method has its own
advantages and disadvantages, and analysis of the first encounter these dosage and precautions in
order to choose a suitable method as mentioned earlier.
SSADM
The SSADM methodology is a well-defined (structured) methodology and is quite difficult to
use. When used skilfully it can produce well-documented, accurate information systems. OR
It can be defined as a systems approach to the analysis and design of information systems.
SSADM was produced for the CCTA, a UK government office concerned with the use of
technology in government, from 1980 onwards. The names "Structured Systems Analysis
and Design Method" and "SSADM" are now Registered Trade Marks of the Office of
Government Commerce (OGC), which is an Office of the United Kingdom's Treasury.





[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 39

The Structure of SSADM:
Logical Data modelling; this is the process of identifying, modelling and
documenting the data requirements of a business information system.
Data Flow modelling; this is the process of identifying, modelling and documenting
how data flows around a business information system.
Entity Event modelling; this is the process of identifying, modelling and documenting
the business events which affect each entity and the sequence in which these events
occur. An Entity/Event Model consists of a set of Entity Life Histories (one for each
entity) and appropriate supporting documentation.

Figure of: Waterfall model methodology:

[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 40

The scope of the SSADM:

SSADM methodology can be used for large and complex projects, because it can provide better
control of the project, it helps in a very short period of time to complete the project.

Objectives OF the SSADM Methodology:

Control AND Improve project management
Make more effective use of experienced and inexperienced development staff
Develop better quality systems
Establish a framework for a good communication between project participants
Make projects resilient to the loss of staff
The advantage of SSADM methodology
SSADM has the ability to reduces the error rate of IS by defining a certain quality level in the
beginning and constantly checking the system.
Well documented procedure.
Also SSADM can provides better control over projects, because it has the rigid structure of the
methodology
Tried and tested tools and techniques
Cross-checking
Involvement of the user
Prescription

[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 41

The disadvantage of SSADM methodology
Long development times as each stage must be completed thoroughly before moving on to the
next. This costs time and money so organizations have to have large resources for SSADM
projects.
Lack of user involvement means the system rarely meets user needs and is less likely to be
accepted.
Bases success on how closely final system meets original specification. Unfortunately business
and user needs change quickly and systems delivered via SSADM are often redundant by the
time they are released.
As it is not iterative, it is sequential changes are not easily implemented, so it's not flexible.
Too much documentation and time consuming overly bureaucratic not everything needs
documenting. This can be a full time job in itself. Also
Time/cost
Limited iteration
No account taken of technological developments
Largely unknown outside the UK
Focus on the current system environment
No account taken of technological developments









[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 42

RAD
Rapid application development (RAD) is a suite of software development methodology
techniques used to expedite software application development.
RAD uses predefined prototyping techniques and tools to produce software applications. It
encompasses a graphical user interface (GUI) development environment, allowing end users to
easily drag and drop required software application components. Also it can be defined as an
approach to building computer system which combines Computer-Assisted Software
Engineering (CASE) tools and techniques, user driven prototyping, and stringent project delivery
time limits into a potent, tested, reliable formula for top-notch quality and productivity. RAD
drastically raises the quality of finished systems while reducing the time it takes to build them.
(Kettemborough1999).

RAD's structure:
Analysis and fast design: rapid design and purpose of the analysis is to collect the necessary
system specifications and provide design rapid growth, according to these specifications, so that
the planning group and user conference will take place between the specifications of the system
began to discuss life. Other conditions, this stage is responsible for creating a specific task
depends on the function of the recommended.
Prototyping cycles: When designers began developing the application of iterative development
cycle, refining requirements and development progress, until the completion of the system
prototype cycle.

Testing: In the testing group and the user tries to achieve the client receives chick test if the
system receives from the user or not.

[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 43

Implementation: In implementation the technical group will connect the system to the website
hosting, after that they will try many tests on the hosting pat to make sure the website and the
system working completely after hosting.



RAD Structure:
The scope of the RAD:

When you need to develop a system quickly without losing a lot of money? , this methodology is
suitable to use it, for large and small projects.



[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 44

The Objectives of RAD:

Developing a system with good quality at a low cost
Analyzing a business process rapidly
To design a workable system solutions through intense between users and developers
collaborate.
In order to get the completed application to the user's hands quickly.

RAD Advantages:
The advantages of RAD are:
RAD realizes an overall reduction in project risk.
Pareto's 80 - 20 Rule usually results in reducing the costs to create a custom system.
It helps to develop a high quality system at low cost and in a short time.
RAD generally incorporates short development cycles - users see the RAD product quickly.
RAD involves user participation thereby increasing chances of early user community acceptance.
Flexible and adaptable to changes
Prototyping applications give users a tangible description from which to judge whether critical
system requirements are being met by the system. Report output can be compared with existing
reports. Data entry forms can be reviewed for completeness of all fields, navigation, data access
(drop down lists, checkboxes, radio buttons, etc.).



[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 45

RAD Disadvantages:
The disadvantages of RAD ARE:
It may be difficult for many important users to commit the time required for success of the RAD
process.
RAD stresses the mechanics of the system itself and does not emphasize the companys strategic
business needs
Cant use for small projects
Requires more resources and money to implement RAD
All applications are not compatible with RAD
RAD is not appropriate hen technical risks are high
Need both customer and developer commitments to complete a project. Otherwise RAD will fail










[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 46

Methodology Chosen (RAD):

Actually after comprising between two methodologies above, we decided to choose RAD
for the assignment because that RAD has the ability to develop to analyze the IT system
more faster and not cost much, however the RAD is really adaptable and flexible with a set
of product specifications and the associated procedures for undertaking the development of
IT systems to support business needs. The method is integrated with a series of supporting
guidelines for customizing the method to reflect different development environments.
RAD realizes an overall reduction in project risk. By the way the RAD generally
incorporates short development cycles - users see the RAD product quickly.
RAD involves user participation thereby increasing chances of early user community
acceptance.


Conclusion:
Briefly when comparing between the SSADM methodologies, we can see that pros and
cons, ,However that is seeming that Spiral has limitations like the size of the project and
the rise cost of the projects which makes RAD the better candidate for APU bookstore ,
because it is a small project that needs less coast and Time.








[SYSTEM DEVELOPMENT METHODS]

[APUs E-Bookstore] Page 47

6.0 Reference

G. Mike & S. Caroline (1995). SSADM, A Practical Approach. England: McGraw-Hill
Publishing Company.
H. Igor (1998). Introduction to Systems Analysis and Design. Australia: Prentice Hall
Australia Pty Ltd.
Inc, C. (2000). What is Rapid Application Development? , 1-34.
Valacich, J. S., George, J. F., & Hoffer, J. A. (2006). Essentials of Systems analysis and
Design. New Jersey: Pearson Education, Inc.
C ASHWORTH AND M GOODLAND, 1990, SSADM-A PRACTICAL APPROACH,
printed in Britain by Richard Clay Ltd, Bungay, Suffolk.
Unknown author, 2011, ASP.net (Visual Basic), available at
http://www.functionx.com/aspnet/index.htm (accessed on 01 Nov 2013).
Paul Allen, 1998, Project Planning & Feasibility Analysis [Online],
Available from <members.aol.com/AllenWeb/planning.htm>
[Accessed on 02 Nov 2013]
Linux Glossary. (2012). Whats GUI. Available:
http://linux.about.com/od/glossary/l/bldef_gui.htm. Last accessed 03 Nov 2013.
techterms. (2012). User Interface. Available:
http://www.techterms.com/definition/user_interface. Last accessed 03 Nov 2013.
Waterfall model. (20Dec2012). Waterfall model. Available: http://en.wikipedia.org/wiki/Waterfall_model.
Last accessed 04-Nov-2013.