Tamera Nikita Sunny 401900628

BSCIT 1 Information Systems 621

19 March 2021

Page 1 of 12
 Table of Contents
Question One 3
1.1. Describe the phases of the system development life cycle. [20 Marks] 3
1.2. Compare the SDLC waterfall model to the spiral model. [15 Marks] 4

Question Two 5
2.1. You are an IT consultant, and you a… structured analysis? [15 Marks] 5
2.2. Briefly explain and differentiate ... application development. [10 Marks] 8

Question Three 10
3.1. Critically analyze … vertical application software. [15 Marks] 10
3.2. Give a detailed account on the … physical design. [15 Marks] 11

Bibliography 12

Page 2 of 12
 Question One
[1.1]
The five phases of the system development life cycle:

1. Planning
This phase focuses on reviewing project requests. It prioritizes the project requests. It
allocates resources to wherever it is needed such as people, money and the equipment to the
approved projects. Forms the project development team that will be taking on the project.
You must understand what needs to done like understanding the problem.

2. Analysis
Conducts preliminary investigation into what is required. The main purpose of preliminary
investigation is to determine the exact nature of the problem or improvement and decide
whether it is worth pursuing or not. Performs detailed analysis activities such as studying the
current system, determining the user requirements and recommending solutions to solve the
problem.

3. Design
Acquires the hardware and software required, if it is necessary to do so. Develops the details
of the new or modified system. By this phase it should the planned out.

4. Implementation
It does the development of programs and applications, if necessary. Implementation involves
creating or getting the various system components like the hardware, software and databases.
Installs and tests the new system. Trains users that will be working it. If the new system is a
success then, convert to the new system. The solution is built or if available to be bought, it
shall then replace the old system.

5. Support and Security

Performs the maintenance activities for the system. Monitors the systems performance.
Assess the systems security. The new system is evaluated. The purpose of maintenance is to
review, check and modify the system so that it continues to meet changing business needs.
[ CITATION cno17 \l 2057 ]

[1.2]
Page 3 of 12
 Compare the SDLC waterfall model to the spiral model:
The Waterfall model:
 In the software development life cycle, business requirements are frozen after the
initial phase.
 In terms of project execution, there is a high level of risk and uncertainty because of
the missing stringent risk management.
 The Waterfall framework type is more of a linear sequential model.
 It is easy to understand.
 Widely known and more commonly used.

 Phases:
 Requirement gathering and analysis
 Design
 Coding
 System integration
 Testing and debugging
 Delivery
 Maintenance
Whereas,
The spiral model:
 Requirements are not frozen by the end of the initial phase. It is kind of executed in a
continuous mode.
 By design, the spiral model is modelled to handle better risk management.
 Spiral model does not follow the sequential stages it follows the evolutionary way.
 Cost involved in this model is usually high.

 Phases:
 Planning
 Risk analysis
 Engineering
 Coding and implementation
 Evaluation (Oreily.com.,
2018)
In conclusion the major difference between these software process models waterfall and
the spiral is that the waterfall model is comprised of the separate and isolate phases of
specification and development. On the other hand, in a spiral model the different
specification, development and validation phases are interleaved. Waterfall model is also
known as classical or linear model because it follows sequential stages while the spiral
model does not follow the sequential stages it follows the evolutionary way. Waterfall
model works in sequential method. While spiral model works in evolutionary method.
(GeeksforGeeks, 2021) 

Page 4 of 12
 Question Two
[2.1]
Creating a new system for a small real estate brokerage firm using an object-oriented approach:

How to begin:
Creating new system with object oriented approach

 Object-oriented approach is methodology which is based on concepts of object,

inheritance, class, attributes, polymorphism and methods.
 Object-Oriented analysis is used for describing the information system by the help of
object. An object can be a place, person, transaction or event.
 Object-Oriented analysis is important than agile method and structured analysis
because it can easily integrate with object oriented programming language like C++,
Perl, java and SmartTalk. (Henderson, J., Iskander, J. & Zhou, J., n.d)
 In the object-oriented approach, the focus is on capturing the structure and behavior
of information systems into small modules that combines both data and process.
 The main aim of Object Oriented Design (OOD) is to improve the quality and
productivity of system analysis and design by making it more usable.
 In analysis phase, OO models are used to fill the gap between problem and solution. It
performs well in situation where systems are undergoing continuous design, adaption,
and maintenance. It identifies the objects in problem domain, classifying them in
terms of data and behavior.

The OO model is beneficial in the following ways:

 It facilitates changes in the system at low cost.
 It promotes the reuse of components.
 It simplifies the problem of integrating components to configure large system.
 It simplifies the design of distributed systems.

 Features of Object-Oriented System:

An object-oriented system comes with several great features which are discussed below.
1. Encapsulation- is a process of information hiding. It is simply the combination of
process and data into a single entity. Data of an object is hidden from the rest of the
system and available only through the services of the class. It allows improvement or
modification of methods used by objects without affecting other parts of a system.

2. Abstraction- It is a process of taking or selecting necessary method and attributes to

specify the object. It focuses on essential characteristics of an object relative to
perspective of user.

Page 5 of 12
 3. Relationships- All the classes in the system are related with each other. The objects do
not exist in isolation, they exist in relationship with other objects.
There are three types of object relationships −

 Aggregation − It indicates relationship between a whole and its parts.

 Association − In this, two classes are related or connected in some way such as one class
works with another to perform a task or one class acts upon other class.

 Generalization − the child class is based on parent class. It indicates that two classes are
similar but have some differences.

4. Inheritance- Inheritance is a great feature that allows to create sub-classes from an

existing class by inheriting the attributes and/or operations of existing classes.

5. Polymorphism and Dynamic Binding- Polymorphism is the ability to take on many

different forms. It applies to both objects and operations. A polymorphic object is one
who true type hides within a super or parent class. In polymorphic operation, the
operation may be carried out differently by different classes of objects. It allows us to
manipulate objects of different classes by knowing only their common properties.

Now using the object-oriented approach I would begin by conducting system analysis, which is
the first phase in object modelling

o System analysis is important because it’s the phase where developer interacts with the
user of the system to find out the user requirements and also do an analysis to
understand the functionality of the system.
o If I don’t properly define the requirements it will cause problems down the line.
o Following system analysis, I would move on to system design. System Design is the next
development stage where the overall architecture of the desired system is decided.
o The system is organized as a set of sub systems interacting with each other.
o While designing the system as a set of interacting subsystems, the analyst takes care of
specifications as observed in system analysis as well as what is required out of the new
system by the end user.
o As the basic philosophy of Object-Oriented method of system analysis is to perceive the
system.
o Then I will begin each of the remaining phase of the object oriented approach one by one
as a system viewed as a set of objectives and has 5 phases:
 Analysis
 Construction
 Testing
 UML
 Maintenance
(Turtorialspoint, 2021)

Page 6 of 12
How are object-oriented tasks different from traditional structured analysis:

Traditional approach Object-oriented approach

Used to develop the traditional projects Used to develop object-oriented projects
that uses procedural programming that depends the object-oriented
programming
Uses common processes Uses UML notations
Depends on the size of the projects and Depends on the experience of the team and
type of the project difficulty of projects
Needs a lot of time sometimes to develop Needs more time than the traditional
the large projects approach and the cost is higher
It works with Top-down approach. It works with Bottom-up approach.
Program is divided into number of Program is organized by having number of
submodules or functions. classes and objects.
Function call is used. Message passing is used.
Software reuse is not possible. Reusability is possible.
Structured design programming usually left Object oriented design programming done
until end phases. concurrently with other phases.
Structured Design is more suitable for It is suitable for in-house development.
offshoring.
It shows clear transition from design to Not so clear transition from design to
implementation. implementation.
It is suitable for real time system, It is suitable for most business applications,
embedded system and projects where game development projects, which are
objects are not the most useful level of expected to customize or extended.
abstraction.
DFD & E-R diagram model the data. Class diagram, sequence diagram, state
chart diagram, and use cases all contribute.
In this, projects can be managed easily due In this approach, projects can be difficult to
to clearly identifiable phases. manage due to uncertain transitions
between phase.

(Turtorialspoint, 2021)

Page 7 of 12
 [2.2]
Explanation and differentiation between Joint application development and rapid application
development:

Joint Application Development:

o Joint application development involves the client or end user in the design and
development of an application, through a succession of collaborative workshops known as
JAD sessions or in other words, a group information gathering technique of systems
development.
o JAD was developed by IBM in the late 1970s originally as a process for designing computer-
based systems.
o JAD centres more on people than on technology.
o By following a structured method that utilizes group dynamics, electronic software, visual
aids and software modeling tools, JAD encourages a partnership between business clients,
management and IS personnel.
o A typical JAD session can last between four days and an entire week and is usually held
away from the main office. A typical JAD team is has five to eight roles depending on the
project.

The roles are:

o ·       Facilitator or the Session Leader

o ·       Scribe or Documentation Expert

o ·       Project Manager

o ·       End User or Client Representatives

o ·       Systems Analyst

o ·       IT and/or IS Representatives

o ·       Executive Sponsor

o ·       Outside Observers

Page 8 of 12
 Rapid Application Development:

o Reduces the time taken to develop an application, focuses more on software

development.
o This application development methodology goes further than JAD in reducing the time
taken to develop an application, is not always as structured as the JAD and focuses more
on software development than JAD. 
o Rapid Application Development is defined as a methodology created to radically decrease
the time needed to design and implement information systems by relying on extensive
user involvement, JAD sessions, prototyping, integrated CASE tools, and code generators.
o  RAD is based on the concept that systems can be developed faster and of higher quality
by gathering requirements through workshops or focus groups, prototyping and early,
reiterative user testing of designs, use of already existing software components and less
formality in reviews and other team communication
o RAD uses small integrated teams of developers, end users and IT technical resources and
short iterative development cycles to optimize its goals of speed, effective informal
communication, unity of vision and purpose, and simple project management. This, when
compared to the traditional SDLC is shorter in delivery and offers better interaction
between users and developers.

(Hoffer, G, 2018)

Differences between the two development methods:

 Joint application development

 More expensive
 Large number of people can be involved
 Suitable for dynamic system development
 Only manager level decision will be taken

 Rapid application development

 Less expensive
 Few people can be involved in software development
 Suitable for unstructured project
 Any developer can take decision at lowest level

In conclusion using JAD and RAD together represents a good way to achieve customers and
business needs for quality and spend.

Page 9 of 12
 Question Three
[3.1]
Difference between horizontal application software and vertical application software:

Horizontal application software Vertical application software

Horizontal application software provides
Vertical applications are written for particular market
solutions based upon the common needs of many
or industry.
companies.
In vertical application software, for performing test,
In horizontal application, use of demo copy for
many days or weeks can be needed by the IT staff and
entering few transactions can be acceptable test.
its team.
Horizontal application software is not business Vertical application software is business specific and
specific and can be used by various domains. designed for specific domain.
Horizontal application software are used for small
Vertical application systems are used for large systems.
systems.
Horizontal application software are easy to use Vertical application software are more complicated
and maintain. than horizontal application system

(Rosenblatt, H, 2018)

In conclusion application software is composed of many diverse types of packages, each of which has its
own specific task. Vertical markets are industry-specific meaning they focus on one particular industry and
are designed specifically to meet the needs of a particular marketing sector, such as financial,
telecommunications or transportation. They may cater to a core group of clientele. This is very different
from horizontal market software, which is designed to be used across a wide range of industries.
Applications in the category of horizontal market segment are more flexible and can be applied more
broadly, as opposed to vertical market software. Vertical market is industry-specific while horizontal
market segments cut across industry boundaries. Today, majority of e-markets are vertically structured,
but horizontal markets are also beginning to expand.

[3.2]

Page 10 of 12
 Relationship between logical and physical design:
Logical design:

 The logical design of the information system helps in defining the features and functions of the
system and also defines the relationship among the components “we must take place” is defined by
the logical design.
 Logical design is not concerned about the way in which the tasks are complete. The method of
implementation is not included in the logical design.
 The logical design defines the functions and features of the system and the relationships among its
components.
 Logical design done during the system analysis phase.
 Logical design includes:
 Output that must be produced by the system
 Input needed by the system
 Process that must be performed by the system, without regard to how tasks
will be accomplished physically
Physical design:
 The physical design of the info helps in defining the way in which tasks are completed.
 The process for storing, entering and verifying data is described by the physical design.
 The sorting procedures and the layout of data files and format of reports are also described
by the physical design.
 The physical design of an information system is a plan for the actual implementation of the
system
 The physical design is built on the system’s logical design and describes a specific
implementation
 System design usually begins after completing system analysis phase
 Some overlap is possible, you might return to fact-finding if you discover that you overlooked
an important issue, if user have significant new needs, or if legal or governmental
requirements change
 Physical design describes:
 Input design
 Output design
 Interface design
 Report design
 Actual processes of entering, verifying, and storing data
 Physical layout of data files
 Sorting procedures
(Rosenblatt, H, 2018)
In conclusion, the systems analyst must understand the logical design of the system before
beginning the physical design of any one component.

Bibliography
Page 11 of 12
C.Noah. (2017) Information Systems – SDLC. Pp 71-72 86-87

 GeeksforGeeks. (2021) Difference between Waterfall Model and Spiral Model - GeeksforGeeks.

[Online] Available from: https://www.geeksforgeeks.org/difference-between-waterfall-model-and-
spiral-model/ [Date accessed: 04 March 2021].

Oreily.com. (2018) Enterprise application architecture [Online]. Available from:

https://www.oreilly.com/library/view/enterprise-application-
architecture/9781786468888/55268c3f-97ed-48f9-bb3f-4c841b57aa6a.xhtml  [Date accessed: 04
March 2021].

Henderson, J., Iskander, J. & Zhou, J., (n.d) Prezi. [Online]

Available from: https://prezi.com/m/mpgan1xjsphw/traditional-approach-vs-object-oriented/
[Date accessed: 16 March 2021].

Hoffer, G. (2018) umsl. [Online]

Available from: https://www.umsl.edu/~sauterv/analysis/488_f02_papers/JADandRAD.html
[Date accessed 15 March 2021].

Rosenblatt, H. (2018) chegg. [Online]

Available from: https://www.chegg.com/homework-help/explain-relationship-logical-physical-
design-chapter-7-problem-10q-solution-9781285422701-exc
[Date accessed 15 March 2021].

Turtorialspoint. (2021) System analysis and design object oriented approach [Online]
Avaliable from:
https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_object
_oriented_approach.htm#:~:text=In%20the%20object%2Doriented%20approach,combines
%20both%20data%20and%20process.&text=It%20identifies%20the%20objects%20in,terms%20of
%20data%20and%20behavior. [Date accessed: 10 March 2021]

Rosenblatt, H. (2018) chegg. [Online]

Available from: https://www.chegg.com/homework-help/explain-difference-horizontal-vertical-
application-software-chapter-7-problem-2q-solution-9781285422701-exc
[Date accessed: 17 March 2021].

Page 12 of 12