Traditional and Agile Systems Analysis Methodologies

This document discusses the traditional and agile systems analysis methodologies. It covers the principles of traditional system development life cycle models and the feasibility study for a system. It also explores the analysis of a system using a suitable methodology and the system design according to user requirements and system requirements.

qwertyuiopasdfghjklzxcvbnmqw
ertyuiopasdfghjklzxcvbnmqwert
yuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiopa
sdfghjklzxcvbnmqwertyuiopasdf
ghjklzxcvbnmqwertyuiopasdfghj
klzxcvbnmqwertyuiopasdfghjklz
xcvbnmqwertyuiopasdfghjklzxcv
bnmqwertyuiopasdfghjklzxcvbn
mqwertyuiopasdfghjklzxcvbnmq
wertyuiopasdfghjklzxcvbnmqwer
tyuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiopa
sdfghjklzxcvbnmqwertyuiopasdf
ghjklzxcvbnmqwertyuiopasdfghj
klzxcvbnmqwertyuiopasdfghjklz
xcvbnmrtyuiopasdfghjklzxcvbnm
qwertyuiopasdfghjklzxcvbnmqw
System Analysis and Design
Database
5/25/2019

Contents
TRADITIONAL AND AGILE SYSTEMS ANALYSIS METHODOLOGIES.........................................................3
TRADITIONAL SYSTEMS ANALYSIS METHODOLOGY...........................................................................3
Principles of Traditional System Development Life Cycle Models.................................................4
AGILE METHODOLOGY......................................................................................................................6
Principles of Agile Methodology Models.......................................................................................7
Comparison & Contrast Between Traditional and Agile Systems....................................................12
FEASIBILITY STUDY FOR A SYSTEM FOR A BUSINESS-RELATED PROBLEM...........................................13
Elements of a Business Case........................................................................................................13
Desirability, Viability and Feasibility of Systems..........................................................................13
Investigation Techniques to Use......................................................................................................14
Criteria to Consider for a Business Case:.........................................................................................14
Vision...........................................................................................................................................14
Goals............................................................................................................................................14
Cost-Benefit Analysis...................................................................................................................15
Benefit.........................................................................................................................................15
Legal............................................................................................................................................15
Economic Considerations............................................................................................................15
Technical Considerations.............................................................................................................16
Operational Considerations.........................................................................................................16
Timeframes Considerations.........................................................................................................16
Organizational Considerations.....................................................................................................17
Security Considerations...............................................................................................................17
Evaluation of Relevance of Feasibility Criteria.................................................................................17
ANALYSIS OF SYSTEM USING SUITABLE METHODOLOGY....................................................................17
Identifying User Requirements........................................................................................................18
User 1 - Management..................................................................................................................18
Requirements...............................................................................................................................18
User 2 – Customer.......................................................................................................................18
User 3 – Supplier..........................................................................................................................19
Identifying System Requirements....................................................................................................19
Functional Requirements.............................................................................................................19
Non-Functional Requirements.....................................................................................................19

Management Requirements........................................................................................................19
Customer Requirements..............................................................................................................20
Supplier Requirements................................................................................................................20
Identifying Constraints.....................................................................................................................20
Roles and Responsibilities............................................................................................................20
Sign off conditions Documentation and Determination..................................................................21
Documentation and Determination.............................................................................................21
Options to the Clint, Nina................................................................................................................22
Criteria to Use to Determine the Suitability of Methodology to Analyse the System......................22
Effectiveness of the analysis in the context of the methodology....................................................23
SYSTEM DESIGN ACCORDING TO USER REQUIREMENTS AND SYSTEM REQUIREMETNS.....................24
Project Plan and Design...................................................................................................................24
Project flow:................................................................................................................................25
Project Flow and Objectives........................................................................................................25
System Design and Document.........................................................................................................26
Interface Design...........................................................................................................................26
Database Design..........................................................................................................................40
Design Documentation....................................................................................................................41
Effectiveness of the System Design with Selected Methodology....................................................41
REFERENCES........................................................................................................................................42
TRADITIONAL AND AGILE SYSTEMS ANALYSIS
METHODOLOGIES
TRADITIONAL SYSTEMS ANALYSIS METHODOLOGY
The traditional software development life cycle has been almost obsolete i
The typical traditional systems lifecycle has become oldest method for information systems
building. However, the same has been in use even today in the projects, medium to larger
complex systems.

Principles of Traditional System Development Life Cycle Models
Waterfall
It is a formal approach considered to build a system, systems development dividing into
formal stages taken sequentially. Here sequentially refers to completing all the activities at
one stage, prior to beginning of the following stage. It shows formal and clear division of
labour in between information systems specialists and end users. This model emphasizes
paperwork with detailed formal specifications generating and accumulating several
documents in the system project course.
Once the system gets installed and enters into production, a formal post implementation audit
takes place with technical specialists and users to determine whether the original objectives
are met and how is it done, along with the exploration of the need for modifications or
revisions. Then the system would be fine tuned in terms of meeting the requirements,
correcting the errors, improvement of efficiency of processing. Once the system gets
stabilized, consistent maintenance is taken place, until the end of its life.
This traditional SDLC model is used still to build medium to larger complex systems, which
demand predefined specifications, formal and rigorous requirements analysis and tight
systems building process controls.
Strengths
- Progress can be measured, according to the complete project scope.
- The client is clear about the progress of the project, as the dimensions, timeline
and cost of the project are clear and shows the progress.
- Any time the client is aware of what exactly to expect according to the inputs
given.
Weaknesses
- This approach of systems lifecycle is very costly
- The entire model is inflexible
- The model consumes very long time
- The model demands specifications to freeze at earlier stages, as the process
discourage changes.
- The waterfall approach is less suitable for several desktop systems that tend to
more individualized and less structured.

Prototyping
The prototyping model involves an experimental system building inexpensively and rapidly
to evaluate for end users. Users can refine and better tune the information requirements by
interacting with the prototype. The users can endorse prototype as a template for final system
creation.
The prototype is meant and considered as only a preliminary model, though it stands as a
working version of part of the system or information system. After the prototype becomes
operational it is still refined further until user requirements are confirmed precisely. After
finalizing the design, the prototype is transitioned to a refined and polished production
system.
The model involves iterative process for development of the system. Planned iterations
replace unplanned rework in prototyping, with each version reflecting the requirements of the
users, more accurately.
Strengths
- Prototyping has the capability to build the system, even there is any uncertainty
regarding designs solutions or requirements.
- The model has the capability to produce the systems fulfilling the requirements of
the user.
Weaknesses
- Prototyping may not accommodate data in larger quantities easily in a production
environment, in case of hastily constructed systems, especially.
- Forecasting the total project duration and completion project date is troublesome.
Spiral
Spiral methodology reflects the tasks relationship with increased parallelism, concurrency in
the activities of design and build and rapid prototyping. And it allows planning methodically,
identifying tasks and deliverables for each of the step in the model. Actually, Spiral
methodology has been developed to fix the drawbacks associated with the Waterfall
methodology.
The Spiral methodology can perceive development process as ‘peeling the onion’, more
likely as progressing through layers. The phase processes and phases are linear, though its
prototype allows the users to find whether the project is moving on track, should be ended or
sent to previous phase.

The Spiral methodology starts in the central part of the spiral. One completed cycle shows a
single stage of process. The product keeps matured, as the spiral progresses.
Strengths
- The Spiral methodology has the ability to apply to development and maintenance
as well.
- At any stage, it can incorporate with prototyping as an option to reduce reduction
at any of the stages.
- The methodology allows focusing on the existing software reuse.
- It allows going back to the previous stages and also accommodates reworks.
- It allows focusing on eliminating or removing unattractive alternatives and errors
at earlier stages.
Weaknesses
- The methodology relies more on risk assessment expertise of the project
professionals.
- It is less effective to work optimally with contracts of fixed price.
- Even for general use, it demands refinement.
- It demands the management to be more wary in terms of control.
- It is less effective and difficult to be used by systems integrators and outside
contractors.
AGILE METHODOLOGY
Agile methodology is preferred and implemented by several business organizations. The agile
methodology follows the following key concepts.
(Ambler and Lines, 2012)
- User stories
- Incremental development
- Daily meeting
- Team active involvement
- Iterative development
- Milestone retrospection
- Personas

Principles of Agile Methodology Models
Agile process is a development process, which develops the system on the basis of
incrementing and iterating, where the requirements can be changed as per the needs of the
customer (Dennis and Wixom, 2009). This theoretical framework, through the cycle for
development, promotes, foreseen interactions.
Agile projects are implemented with various methodologies.
Scrum
Scrum stands as one more popular and important agile development method, as the
productivity is expected to be very high with it. The model is developed on the basis of the
process of incremental software development. The total development cycle gets divided in
sprint, which is iteration, in series. Sprint has maximum duration of 30 days.
Strengths
- Scrum has the major strength of being adaptive to the environment that usually
keeps changing.
- The model also ensures customer satisfaction, which is the first priority for many
business organizations.
- The entire model is developed with least documentation.
- The model also minimizes risks of development.
Weaknesses
- Since customer interaction defines the success of the scrum model, in case
customer inputs are unclear or inconsistent, the development cycle of the model
hinders.
- Least documentation itself is weakness, as detailed changes of design in every
iteration cannot be recorded.
- Constant changes of the requirements consume more than enough time and it is
also wastes of resources.
- The model and process is less helpful to the developer, though is helpful to the
management, in terms of taking the decisions.
Extreme Programming (XP)
Extreme Programming is one of the most successful and preferred agile software developing
methodology, since it has customer satisfaction as the major focus. The principle it follows is
that the entire life cycle of software development is divided into multiple and short cycles of

development (Dan et al., 2014). At any phase of this cycle, it incorporates and welcomes
requirements or changes proposed by the customers.
XP follows simple values, such as courage, feedback, communication and simplicity.
Strengths
- XP enables the process to quick and high-quality delivery of the outcomes
- The delivery of the outcomes are continous.
- The model allows best outcome, as customer involvement is high and because of
rapid feedback loops, close teamwork with coninous planning.
Weaknesses
- It demands more training and talent.
- Organizational transformation to this model from an existing traditional SDLC
model needs structural transformation.
- Scalability is a troublesome, unless specific models are followed.
Lean
Lean methodology offers the features of solid conceptual principles, values and frameworks,
along with fair practices. This methodology works basically on reducing the waste .
The methodology involves the process that is divided into three activities value-adding, non-
value adding and essential non-value adding (Ladas & Corey, 2007). Here, the activities
involved in the activity called non-value adding is considered to be waste and so these
activities are tried to remove, considering it as waste, so that the entire model is made as
leaner. Hence delivery becomes faster with lesser wasted efforts.
Strengths
- Improved efficiency in the process of development, because of elimination of the
waste.
- The same also speeds up the software development process, which in turn reduces
cost and time of the project.
- Faster product delivery, which means delivery of more productivity earlier.
- Development team empowerment helps to develop the team’s ability of decision
making, which would also motivate the team.

Weaknesses
- The project is more dependent over the team’s cohesiveness and the team
member’s individual commitment.
- The overall success of the project is highly dependent over the team members’
discipline and also on their technical expertise.
- The model demands to evolve the requirements specification very clear.
- Too much flexibility may lead to deviate from the original objectives of the
project.
Scaled Agile Frameworks (SAFe)
SAFe is developed to bring the final and better products faster in the market. SAFe calls for
alignment and closer collaboration across the teams and has the objective of centralized
decision making. The model offers options for multiple configuration on the basis of the team
size. It includes the process in three levels, called Team, Program and Portfolio.
Strengths
- SAFe allows ‘big picture’ visualization by organizations, through roles and
responsibilities mapping and required activities for development of the software.
While doing the same, organizations explore answer the questions related to the
alignment of the initiatives of software development with objectives of business or
the predictability of the same.
- Unlike many models, it helps to pinpoint opportunities for workflow improvement
and also to measure success.
Weaknesses
- It is considered to be too much top down approach.
- The model calls for roles of administration to oversee coordination of multiple
projects, dependencies and releases.
- It can slow down the processes.
Kanban
Kanban method or framework has been adopted and more prominent in the testing method
for software, especially in agile testing. Kanban means simply a card and it contains the work
details related to the software. The objective of this methodology is visualization.

Kanban cards are majorly used by the teams for continuous delivery. Kanban is similar to
Scrum, where it helps effective work by teams and promotes collaborative and self-managed
teams (Cacaniti & Daniel, 2018).
Karban has three basic principles, visualizing the workflow, limiting the work in progress,
enhancing the flow.
Strengths
- Kanban methodology promotes encourages ongoing and active learning and
continuous collaboration.
- The model offers best possible workflow for the team.
Weaknesses
- The model is less effective in situations of shared resources.
- The process may become ineffective with infrequent orders.
- Quality miscues
- It has more problems associated with the production flow.
- It cannot eliminate variability.
Disciplined Agile Delivery (DAD)
Disciplined Agile Delivery aims in addressing the areas that not found with the agile
frameworks of smaller scale. This model progresses the process in three phases called,
Inception, Construction and Transition.
Strengths
- The major strength of the DAD is recommending the processes at the phase of
inception and also in transition, where the teams prepare for delivery.
- More guidance in the architectural and design area.
- It also allows enough flexibility in terms of various guidelines for processes for
the lifecycles of systems development.
Weaknesses
- Marketplace adoption is slower for DAD, especially when compared with SAFe
framework.
- The model demands experienced consultants and coaches compared to the other
models.

Agile Modelling (AM)
Agile Modeling is basically developed to perform modelling activities and has major focus
on cultural principles and practices. The key idea of AM is to produce models that are
advanced enough for supporting acute problems related to design and purposes of
documentation, while maintaining lower amounts of documentation and models. The model
has major focus on cultural issues and the same gets reflected in the team structures and
support for communication and team working spirits.
The four values of AM include courage, feedback, simplicity and communications, which are
similar to the Extreme Programming. It follows best practices in four categories, simplicity,
teamwork, iterative & incremental modelling and validation.
Strengths
- Cultural aspects are given emphasis that influence the outcomes as well as
practices.
- The model supports day to day duties of software development.
Weaknesses
- AM is insufficient along itself, from viewpoint of broader software development.
- The model covers only modelling and so demands supporting methods.
- Much more efforts are demanded to illustrate the seamless integration possibilities
with other methodologies of development.
DevOps
DevOps is a combination of practices of software developed. DevOps is the combination of
Software Development (Dev) and Operations of information technology (Ops) and shorten
the process of SDLC and delivers fixes, updates and features that are closely associated and
aligned with the objectives of the business (Loukides & Mike, 2012). The best part of this
technology is that it involves a set of practices that are involved in minimizing the time to
change that would be placed into normal production from committing change to a system,
while high quality is ensured(Andrej et al., 2015).

Strengths
- The DevOps methodology takes very shorter time for marketing
- Allows to work for better product quality
- The model improves efficiency along with the productivity.
- The model allows releasing better reliable outcomes.
- The outcome allows to develop better customer satisfaction.
- The model allows fast experimentation thereby increasing the ability for right
product building.
-
Weaknesses
(Erich et al., 2017)
Comparison & Contrast Between Traditional and Agile
Systems
CHARACT
ERISTIC
TRADITI
ONAL
SDLC
AGILE
METHOD
OLOGY
WATER
FALL
PROTOT
YPING
SPIR
AL
SCRUM EXTREM
E
PROGRA
MMING
LEAN DAD
BASIC
PROCESS
All the
process
goes in a
sequentia
l order,
where
there is a
clear
division
between
Prototype
is the
basic and
fundamen
tal ways
of
implemen
ting the
process
Builds
rapid
protot
yping
with
concur
rent
and
paralle
l task
Scrum
support the
teams to
work
effectively
and
enables
collaborati
ve and
self-
Chopping
major
objective
into
shorter
cycles of
developme
nt
Lean
process
works
with
the
activiti
es
divided
into
value-
Proces
s
follow
s is
incepti
on,
constru
ction
and
transiti

labour
and
specialist
s.
It also
involves
very
detailed
and long
document
ation
relatio
nship
managed
team
promotion
adding,
non-
valye
addign
and
essenti
al non-
value
adding
on
Basic
Strength
Easy to
measure
the
progress
Capabilit
y to build,
even with
design
uncertaint
ies
Allow
s to
reuse
an
existin
g
softwa
re
Adapting
to
continuous
ly
changing
environme
nt
Quick and
high
quality
outcome
and
delivery
Better
efficie
ncy
Better
and
clear
guidan
ce in
the
archite
ctural
and
design
area
Basic
Weakness
Very long
and only
sequentia
l process
Project
duration
forecastin
g is
troubleso
me
Dema
nds
consist
ent
refine
ment
Unclear
input can
hinder the
entire
process
Demands
high level
expertise
and
training
Outco
me is
depend
ent
more
on
team’s
discipli
ne and
commi
tment
Slower
market
adopti
on
Table : Traditional Vs. Agile Methodologies

FEASIBILITY STUDY FOR A SYSTEM FOR A BUSINESS-
RELATED PROBLEM
A business case considered here is Nina Beauty salon. A feasibility study is conducted to
automate the business operations, which have been performed manually. This business
related problem is considered to transition the existing system into an automated system,
through website. In this context, traditional software development life cycle and agile SDLC
are checked to find which one can be the best suitable one. (Hoffer et al., 2015)
Elements of a Business Case
Nina Beauty salon has been owned by Miss Nina and is placed at Golder’s Green Road, 111
A, NW11 8HR, London. The salon is in operation from 10 AM to 6 PM, Fridays and
Saturdays. The salon has the contact number 010 8731 8640. Nina Beauty offers various
services for physical grooming, like Body Treatments, Facial Acne Treatments, Hand
Treatment, Manicure, Scarring and Stretch Marks Treatment, Massages, Lip Treatment, and
so on.
Desirability, Viability and Feasibility of Systems
Problem Identification and Desired Solution
The salon is operated by only one employee, who is the owner of the salon and all the
transactions are recorded manually. The salon maintains transactions in two categories, daily
transactions and periodical transactions. Daily transactions usually include recordings the
details about the customer, bookings and payments. And periodic transactions include a
newly bought product that gets added to the existing products in the salon, along with the
new information about the new procedure. both the daily and periodical transactions demand
reference records in order to analyze the service sales along with the check of the product.
Currently the salon records these transactions manually and so relies on manual recording
system.
Problems to Management
Management and employee, both the same in this business case, Nina has to perform all the
operations manually, such as, to search any customer details, to enter new customer details,
requirements of the customer, procedure to perform for the same customer, outcomes and pay

details for the same service. Among all these manual transactions, searching takes very long
time and it keeps increasing as the customer base keeps increasing. All the calculations take
additional time (Kenneth & Kendall, 2013). Another big challenge is the generation of
revenue reports on monthly and yearly basis, according to the customer base, which
consumes a lot of time and is prone to human errors. The salon is new and the customers will
start reaching and the data gets accumulated.
Problems to Customers and Suppliers
The customers cannot find the availability of desired beauty service, the price list of the
services offered and other service details, until they reach the location. Suppliers cannot find
the details of the cosmetics they use and they have, until they contact the salon owner, and
eventually, offering the deals and existing and new cosmetic products they like to offer.
So, there is a desirability of a new system that would automate the transactions both on daily
and periodical basis and enable visibility of the beauty services of Nina Beauty to the external
world.
Investigation Techniques to Use
There are different techniques used to investigate the user requirements and other
requirements. Various techniques are
1. Investigation
2. Record inspection
3. Interviews
4. Observation
In this feasibility study, interview technique is considered and followed to gather all the
requirements needed for the project.
Criteria to Consider for a Business Case:
Vision
The business case, Nina Beauty salon has the vision of automation of the beauty
services operations and performs day to day and periodical transactions in much less
time and increase the visibility of the business services to more customers and thereby
improving the business operation.

Goals
The Nina Beauty business case has the goal of automation of all the operations done
so far manually and automates customer contact and transactions through the website.
Cost-Benefit Analysis
Cost involved in the automation of the business operations are the following.
S.NO. COST ELEMENT COST
1 Website design and development $1500
2 Training to perform transactions $200
3 Cost of maintenance, website renewal, per
year
$300
4 Content writing services $300
5 Laptop $1000
TOTAL $3300
Benefit
According to the statistics, salon and beauty services have the revenue or benefit of
200% or even more. If the investment of the salon is $10,000, the revenue expected
by end of the year can be $30,000. So, the investment of $3300 can be returned within
one year.
Legal
There are certain legal considerations in automation and maintenance of the
operations with the database and website.
- Concerns of copyright in terms of maintaining the content in the website
- Concerns related to the domain name, where domain name must be according to
the business operations.
- Concerns related to trademark must be considered and followed according to the
legal aspects in respective country, London.
Economic Considerations
In this context, maintenance cost of the salon has to be considered and how much new
system is going to cost including both initial cost and maintenance cost. Economic

analysis is needed for economic justification. Economic considerations can be
justified when the value of the project is weighted with the advantages to the
automation system and in case it justifies the fundamental objective of the
organization, which is making the profit (Marakas & George, 2010).
The project needs to analyze how Nina Beauty salon is strong economically to assure
green signal to develop the project intended. The investment for the automation
system is lesser compared to the investment of the business and the investment can be
obtained within one year.
Technical Considerations
Technical considerations include assessment of technical resources in the
organization. This study helps to assess whether the technical team can automate the
transactions of the business or not. It needs to explore the technical and web
technology expertise, hardware, software and web technologies. The required
hardware is available, in the form of laptop, software is readily available, even by
open source and the most important thing is the technical expertise. Hence, technical
expertise is required to develop the website and perform AMC or Annual
Maintenance Contract (Dennis & Wixom, 2009). Web developer has to be very
efficient and instantly accessible to ensure that the website is developed according to
the requirements and maintained with no technical issues.
Operational Considerations
The operations considerations involve the operations that have to be viable after
development of the project. So, in the case of Nina Beauty salon, automation of the
day to day and periodical transactions must be performed by a single employee cum
owner, Nina. These operations will be different from the manual operations, as it
needs website and website operational familiarity to perform the transactions on
regular basis.
The regular operations Nina has to perform should be database operation and website
update with the services offered, price details, cosmetic products available in the
salon. The necessary technical and website expertise is expected to be developed by
Nina with the necessary training, provided by the website developer.

Timeframes Considerations
Since Nina Beauty is a small scale business and has only a few operations usually
managed by a single person so far, the website requirements are very few. Hence, the
lower requirement website can be designed and developed along with the database
design and integration in maximum two months period.
Organizational Considerations
So far the Nina Beauty is an organization run by a single employee, who is an owner
also. One and only customer for the automation project can provide all the
requirements in a couple of meetings and integration of the requirements can be
easier. All the inputs required and changes required can be made clear with a single
person (Hoffer et al., 2015). So, organizational considerations like the user
requirements can be clear, direct and in limited.
Security Considerations
Since cyber threats have become numerous, security considerations also more in
terms of running the website and sensitive financial transactional data. It demands
serious security checkups and anti-virus aspects.
Evaluation of Relevance of Feasibility Criteria
So, on an overall, feasibility criteria for the Nina Beauty salon has been presented in terms
multiple dimensions, cost-benefit analysis, legal, technical, operational, organizational and
security aspects. In all these criteria, the project of automation is justified as these
considerations have been justified logically and realistically (Marakas & George, 2010).
ANALYSIS OF SYSTEM USING SUITABLE METHODOLOGY
The transaction automation and website development project has the following benefits.
BENEFIT TANGIBLE INTANGIBLE
Automation of transactions Time and efforts to perform
operations can be reduced to
a greater extent.
Quality and speed of
operations can be improved.
Customer database
maintained in Database
Management System
Data accessible easily and
quick
Integration of data, in terms
of customer, services,
payment, revenue, etc.

(DBMS)
Digital platform for salon
through website
The business is accessible to
the world.
Reputation and business
potential improves
Digital business and financial
transactions
Faster and easier payment
methods and transactions
Business hike in terms of
faster and reliable
transactions
Data transparency Data easier to maintain and
transparent legal aspects,
such as tax payment
Increased business potential
and rating in terms of profits
Identifying User Requirements
The project has three different kinds of users, management, customers and suppliers (Davis,
2009).
User 1 - Management
Management is associated with Nina, who is both the owner and workforce for the beauty
services.
Requirements
- Perform day to day and regular transactions in the database
- Access the website as administrative and update the data and add new content
- Connect both the database and website for integrated operations and data
consistency
User 2 – Customer
Customer is the source for running the business and earning the profits in the Nina Beauty
business.
Requirements
- Customer should be able to access all the services, procedures, price list and
success rate of procedures through the website.
- Customer should be able to reserve time slot to get the beauty service.
- Customer should be able to make financial transactions and pay prior to receiving
the services.

- Business statistics to be made available and access through the website.
- Website has to be accessible all the day and night.
User 3 – Supplier
Supplier is involved in supply of the cosmetic products used in this business both to use for
the beauty services and also for resale by the management (Verheyen & Gunther, 2013).
Requirements
- A special tab should be accessible by the registered supplier to get update
regarding the stock of the products.
- Enabling option to send messages to Nina only, about offers, discounts, new
product introductions.
- Receive payments by Nina Beauty to the suppliers online
-
Identifying System Requirements
Functional Requirements
- Database access to be regular and consistent to update the data
- Website administrative rights to update data on website
- Integration of database and website
- Website to be accessible to customer consistently
- Booking time slot by customer any time, by accessing time slots available
- Get price list according to selected beauty services
- Special tab for suppliers to access product stock details
- Communication made possible with the owner
- Financial transactions made possible with the owner
(Johnson & Louise, 2011)
Non-Functional Requirements
- Website should be operational continuously with minimal downtime.
- Website should be enough secured.
- The entire automated system to be robust.
- The website should be user friendly to be easy to use
- Website should be enough feasible to scale up at later stages.

Management Requirements
The management should be able to
- Access and update data in DBMS to update day to day and periodical transactions.
- Access website as administrator and update website content
- Generate daily, monthly and yearly sales reports
- Communicate with the customer and supplier
Customer Requirements
The customers should be able to
- Access the services of Nina Beauty salon
- Communicate with the management
- Select the procedure intended to take
- Get price for selected services and procedures
- Make financial transactions
Supplier Requirements
The suppliers should be able to
- Access the product stock
- Communicate with the administrator
Identifying Constraints
There are constraints associated with any of the project and so the automation and website
development project (Partogi & Joshua, 2013). In this context the constraints are the
following.
- Nina has to be technical to understand the new technology and also the technical
aspects involved in it, since she may be new to information technology.
- Legal aspects, while transitioning the business to the online platform have to be
very carefully considered, otherwise it is inviting unexpected risks.
- She has to be familiar with the technical aspects to maintain the data in computer.
Identifying Team Members, Roles, Responsibilities in A Project Team
Here, according the Nina Beauty salon automation project, there are majorly two groups of
team members involved, Nina, Management and Project Management team.

Roles and Responsibilities
Nina, Manager
- Roles
o She has to enlist the requirements and input every aspect to the website
development team.
o She has to envision business and foresee the new requirements in the
future and add those inputs to the requirements list.
- Responsibilities
o She has to be very clear with the vision and goals and enlist the inputs.
o She is the decision maker to decide whether the project is feasible or not
and proceed accordingly.
o She has to provide all the resources required for completion project and
maintenance of the website.
Project Management Team
- Roles
o Perform feasibility study and submit to Nina, manager
o Gather all the requirements are required and estimate all the resources
required.
o Final website and DBMS must be developed according to the requirement
and submit to the client, Nina.
- Responsibilities
o The project team has to conduct feasibility study and submit to the
manager.
o All the estimations of resources, including time, money and efforts have to
be done realistically and collect the resources.
o Final product should be viable and ensure the functionality to the expected
levels.
Sign off conditions Documentation and Determination
By the time of sign-off condition, the project manager has to ensure the following
documentation and determination (Cohn & Mike, 2010).

Documentation and Determination
Documentation at the sign-off conditions must include the individual and integrated report
about the following.
- It should include the feasibility study about the project.
- All the requirements and estimation of budget, time and human resources required
- The detailed work breakdown structure for development of the website and
DBMS
- The final project outcome and detailed aspects of it
- The total resources utilized for the project
- Detailed training for using the website and database
- Details about the maintenance required and necessary resources required
Options to the Clint, Nina
S.NO. OPTION BENEFIT WEAKNESSES PRICE
1 Continue the
manual data
management
system
Time, effort and
money will be
saved
Less potential
for business
growth and
waste of time,
more efforts
000
2 Create website
and DBMS for
automation
Business
improvement,
increased
reputation and
website reaching
more customers
Technical
expertise
required to
maintain DBMS
and website and
downtime may
trouble the
productivity
$3300
3 Employing an
employee for
data
maintenance
Creating new
employment
opportunity for
one employee
Dependence
over employee
for data
maintenance,
more money to
be spent every
$500 every
month

month
Criteria to Use to Determine the Suitability of Methodology
to Analyse the System
Agile methodology has been decided to apply and implement for this project. Agile
methodology is basically iteration and integration process and in this based on the
requirement of the client, Nina, the processes have been iterated and improved to obtain to a
working and realistic outcome. Agile methodology is actually designed and developed for
information technology applications and website development is one of the IT projects. The
methodology is more efficient and highly collaborative to adopt for the IT project (Arif &
Bob, 2015).
Agile methodology has been used for this project management and implementation because
of the following reasons.
- Agile can give rapid deployment of the project, website.
- It helps to minimize the resources and reduce the waste.
- It allows the project to be flexible, by being adaptable to the changes, like any
new requirements added later.
- Agile helps to detect the issues and defects, during the iteration and integration
process.
- The development process of website can be optimized with Agile.
- It allows to increased collaboration and feedback frequency for the project
implementation.
Effectiveness of the analysis in the context of the
methodology
The Agile methodology used for this project implementation is Scrum. In this context, this
model has been used for the following reasons.
Innovation and Creativity – Though the website and DBMS are needed in this project, best
possible creativity and innovation are demanded, as there is a huge competition for beauty
salons, especially in urban areas. So, to stand at first row in competition best possible
innovation and creativity should be applied and Scrum model allows to apply creativity and
innovation in iterative and integration method.

Scrum is a lightweight, incremental and iterative framework and best suitable for new
product development and so development of a new website and DBMS product development.
Basically Scrum has a key principle and is recognized in two aspects that the customers keep
changing their minds and ideas regarding their expectations about the product, which is also
known to be requirements volatility (Cob, 2015). The unpredictable changes that can be
possible by Nina, client of this project, encouraged for the development of the best product
and to increase the profits of the beauty salon and these changes can be considered and
implemented effectively with the Scrum model.
Another aspect is the self-organization capability of the team members either physically in
one location or through online. Here, the project management team that most probably
includes the website designer and website developer usually, is expected to be smaller in size.
However, though the team is smaller, team members collaboration and online regular
communication is expected and Scrum can be effectively suitable for the same project.
Scrum involves three roles in this framework. The three roles are product owner,
development team and scrum master and all three working together. The role one is Nina,
owner or client of this project, development team and scrum master are expected to be the
project manager, who is accountable for this project.
In this project Scrum has been selected to be the best suitable Agile methodology and the
project uses this process and tools to implement this project.
So, the project is going to be effective with the strengths creativity, time-to-market, lower
prices, improved quality, employee satisfaction and customer satisfaction of Scrum model.
SYSTEM DESIGN ACCORDING TO USER REQUIREMENTS
AND SYSTEM REQUIREMETNS
Product design stands as the first and foremost phase in systems development life cycle. The
design is initially described in a document and the following tasks in the same process
involve making the flow diagrams, followed by making DFDs. This phase is very significant
as it decides and stands accountable to deliver robust and qualitative product.
During the design phase, the primary concept to concentrate is the flow of the tasks related to
the website and DBMS development system. The focus has to be made on the architecture of
the system (Hron & Obwegeser, 2018).

Project Plan and Design
The project plan involves the events of actionable things listing and scheduling the same to
keep the project progressing ahead.
Project flow:
Project Flow and Objectives
The project starts with the proposal of the project. Feasibility study is made about, whether
the project is useful or not. Once the client, Lina approves the feasibility study and report
made and gives green signal to the project implementation, the actual process starts. Next
phase is the identification of the requirement and the actual project implementation starts
here. After the requirements are understood and clear, process to develop the website and
DBMS is done. Once the process is designed and developed, it should be analyzed going
back and forth towards the requirements of the client. After the process is developed and well
analyzed, product is designed, in the sense the website is developed and database is designed.
After the product is designed and developed, it is not the end of the project implementation.
Then, if needed, the entire process of the project is repeated and necessary corrections,
refinements and developments are made.
Finally the objective of developing the website and DBMS should be done.
Design elements for the traditional and agile methodologies. Determining the design
features for traditional and agile methodologies. Data flow diagrams and flow charts.
Porposal of the
Project
Feasibility Study
Identifying the
Requirements
Product Development
Process Design
Analysis of the
Process
Product Design
Review the process
and better it

Determining the tools and techniques relevant for the design of systems for database
applications, web applications, games, mobile applications and other software
applications.
System Design and Document
The system design document consists of the information regarding the following elements.
- Business Rules
- User Design
- Interface Design
- Database Design.
While the traditional system development life cycle uses the above design elements, the same
design elements are used by the Agile methodology also, however, the difference is that these
elements and processes are iterated consistently until the best process is refined (Collier,
2011).
Interface Design
Interface design is the communication tool in between Nina, manager and the customers of
the Nina beauty salon. The interface in this context is the website development. The website
is the digital platform, where Nina, the client places, whatever she wants to communicate
with the customers and the same platform, website is used by the customers to view the
information posted by Nina and respond by ordering the beauty service and procedure. So,
this interface becomes the face of the Nina Beauty salon (Vasiliauskas & Vidas, 2014). The
design of this interface, website has the following functionalities and sub-functionalities.
Page 1: Home Page

Figure 1: Home Page
Figure 1 represents the Home Page of the website, the face of the Nina Beauty salon. This
page has the primary details of the salon, such as the name, logo of the company and also
primary services offered by the company. All the other pages of the website are accessed
from this Home page. The design should be effective that should build a decent feeling and
impression on the business. It is the major functionality of the website and the company.
The same page also allows the customers to select the treatments and proceed with the
services and time slot bookings.
Page 2: About Us
The second page is About Us page, which gives detailed legal and services information about
Nina Beauty. The services offered like the treatments and respective procedures are described
in this page. This functionality of the web page contains two sub-functionalities, ‘Who We
Are’ and ‘Customer Reviews’. The two sub-functionalities are the following two pages.

Figure 2: About Us Page Moving To ‘Who We Are’
Another page of the About Us page directs is the ‘Customer Reviews’, which displays the
reviews made by the existing customers. This page is shown below. This review helps to find
the facts and experiences about the services provided by the Nina Beauty salon and then take
the decision to whether to experience these services.

Figure : ‘About Us’ page moving forward to ‘Customer Reviews’
Page 3: Customer Login / Register Page

The next following important page is Customer Login / Register page. This webpage allows
the existing customers to login directly and book a service with time slot. If the customer is
new to the salon, one can register with the basic details like name, contact details, email id
and residence details. Then one can book service and timeslot, as needed.
Page 4: Treatment Page

Figure : Treatment Page
From the Home page, ‘Treatment’ Page can be accessed. This page displays all the details of
the services and procedures offered by Nina Beauty salon. This Treatment Page functionality
has multiple sub-functionalities, like different treatments offered by the salon. The Treatment
page directs to three different pages, ‘Facials’, ‘Massages’ and ‘Body Treatments’
Page 5: Facials directed from ‘Treatment’ Page
This page contains the list of Facials displayed in each page, as the following.

Internal Pages – Facials page directs to different facial treatment pages, as shown in the
following table.

Figure : Three Facial pages directed from Facial page, from Treatments
Page 5: Massages Pages
The Massages pages are directed from Treatment page and it contains the following pages
directed to.

Page 6: Body Treatments
The Body Treatment page is directed from Treatments page and it redirects to the following
page.

Page 7: Gallery Page
The Gallery page is directed from Treatment page and it contains images of the beauty
services performed and the same advertise the business and services.

Figure: Gallery Page
Page 7: Contact Us Page
‘Contact Us’ page is mandatory to almost all the website, where if anyone with the business
or without business intentions want to communicate with the owner of the business, they can
contact with them, through mail or by taking the contact number of the salon or Nina.
Another important page is the ‘Terms and Conditions’, which is important for every website.
This page is needed to display the terms and conditions of the services they offer and content
of the website and usage of the cookies of hosting computer.

Database Design
The Nina Beauty salon has to maintain the database and the data and transactions must be
managed in the form of tables. These tables are created in Microsoft Excel.
Table 1: Treatments Table
This table contains the data about the details of the treatments offered by Nina Beauty salon.
Treatment Cateogory
Cos
t
Time Duration in
Hours
ESPA Facial Facial
$10
0 01:30
DECLEOR Facial Facial
$12
0 02:00
Guinot Facial Facial $80 01:00
ESPA Massage Massage $75 01:15
LAVA SHELL
Massage Massage $80 01:45
ESPA Body
Treatment
Body
Treatment
$20
0 03:00
Table 1: Treatments
Table 2: Customer Table
The details of the customer are maintained in the Customer table and all the details of the
customers are maintained here.
Customer
ID
Customer
Name
Contact
Number
Date of
Contact
Date of Last
Visit
Procedures
Undergone
1001 ABC
XXX-XXX-
XXX 01-Feb-18 01-Dec-18 Massage, Facial
1002 BBA
XXX-XXX-
XXX 01-Feb-18 06-Dec-18 Facial
1003 ABB
XXX-XXX-
XXX 01-Feb-18 12-Dec-18 Body Treatment
1004 BBC
XXX-XXX-
XXX 02-Feb-18 17-Dec-18
Facial, Body
Treatment
1005 CCA
XXX-XXX-
XXX 03-Feb-18 18-Dec-18 Massage
Table 2: Customer

Table 3: Expenses table
The day to day expenses have to be recorded in a table.
Date of
Expense
Expense
Item
Categor
y
Amou
nt
01-Dec-18 Product 1 Massage $300
01-Dec-18 Rent Office $500
02-Dec-18 Maid Office $200
Table 3: Expenses Table
Table 4: Income Table
Income incurred from every treatment has to be recorded in the table.
Date Income Item Category
Amount
in $
Taxable
Amount
Revenu
e
01-
Dec-18 ESPA Facial Facial 100 10 90
01-
Dec-18 ESPA Massage Massage 75 7.5 67.5
02-
Dec-18
ESPA Body
Treatment
Body
Treatment 200 20 180
Table 4: Income Table
Design Documentation
Two major documents are to be maintained, Website and Database.
Website documentation contains all the web pages developed according to the user
requirement and database with all the tables with all the pages and tables shown above.
Effectiveness of the System Design with Selected
Methodology
The website and database project has been implemented with the Agile development model,
added with progressive model. Hence the entire website and database are developed in

speedy and progressive cycles. The customer can register and login to the Nina Beauty
website and journey through the beauty salon services. The database is used to maintain the
day to day and periodical transactions associated with the salon. The website stands as a
faster and easier communication tool between the salon owner and customer.
The manager, Nina has all the administrative privileges and so all the content is readily
accessible and allowed to update, according to the requirements. So, the website content is
enough flexible and whenever any changes about the services and procedures Nina wants to
offer and change, the respective changes can be affected immediately, done by herself.
Potential customer can get the details of all the services and procedures. Existing customers
can readily login and seek for the services and timeslot.
The organization needs to be refined and consistently seek reliable knowledge about the same
business for effective decision making. The same website can be used by the administrator,
Nina to update various deals and offers to the customers.
When data is organized as information, it becomes the basic source, where meaningful
information and desirable knowledge can be obtained. Every individual makes use of data in
database, like telephone book, dictionary, books catalogue, etc. and are some of the examples
of the databases. The database management system package enables the manager to maintain
day to day and periodical transactions. The objective of this website and web software is for
producing an effective and convenient methodology of retrieving, storing and shaping the
knowledge in the data. The website also can interact and interface with the database
management system, with only important data to be connected. The database exerts
centralized management of all the data and also prevents unauthorized customers from
information access and privacy info is ensured.
Each of the activity and process has been implemented according to SDLC, a framework and
on the basis of the same, project is implemented and works as the final website and database
development project. Finally, the organization enables transactions managed as a database
and communicate with customers through the website.
REFERENCES
1. Ahmed, A. Ahmad, S. Dr. Ehsan, N. Mirza, E. and Sarwar, S.Z. (2010). Agile
Software Development. Impact on Productivity and Quality, in the Proceedings of
IEEE ICMIT.

2. Ambler, S. and Lines, M. (2012). Disciplined Agile Delivery (DAD) A Practitioner’s
Guide to Agile Software Delivery in the Enterprise. IBM Press.
3. Andrej, D. Ralf, P. Horst, L. (2015). Towards Definitions for Release Engineering
and DevOps. Proceedings of the 2015 IEEE/ACM 3rd International Workshop on
Release Engineering.
4. Arif, G. Bob, H. (2015). Agile SCRUM For Denver Web Development. Neon Rain
Interactive.
5. Cho, L. (2009). Adopting an Agile Culture A User Experience Team's Journey. Agile
Conference. pp. 416–421
6. Cobb, C. G. (2015). The Project Manager's Guide to Mastering Agile: Principles and
Practices for an Adaptive Approach. John Wiley & Sons.
7. Cohn, Mike. (2010). Succeeding with Agile: Software Development Using Scrum. Upper
Saddle River, NJ: Addison-Wesley.
8. Collier, K. W. (2011). Agile Analytics: A Value-Driven Approach to Business Intelligence
and Data Warehousing. Pearson Education.
9. Dan, T. Robert, F. Bernhard, R. (2014) Limitations of Agile Software
Processes. Proceedings of the Third International Conference on Extreme Programming
and Flexible Processes in Software Engineering: 43–46.
10. Davies P. B. (2009). Business Information Systems. Palgrave, Basingstoke.
11. Deemer, P. Benefield, G. Larman, C. Vodde, B. (December 17, 2012). The Scrum
Primer: A Lightweight Guide to the Theory and Practice of Scrum (Version 2.0). InfoQ.
12. Dennis, A. and Wixom, B. (2009). Systems Analysis and Design. 4th Ed. International
Student Version. John Wiley & Sons.
13. Dingsøyr, T., Tore Dybå, T. and Moe, N.B. (eds) (2010). Agile Software
Development. Current Research and Future Directions. Springer.
14. Erich, F.M.A. Amrit, C. Daneva, M. (June 2017). A Qualitative Study of DevOps
Usage in Practice. Journal of Software: Evolution and Process
15. Gertrud, B. Jim, C. (2008). Scrum as Organizational Patterns. Gertrude & Cope.
16. Gwanhoo, L. Weidong, X. (2010). Toward Agile: An Integrated Analysis of Quantitative
and Qualitative Field Data on Software Development Agility. MIS Quarterly.
17. Higgins, Tony (2009). Authoring Requirements in an Agile World. BA Times.
18. Hoffer, J., George, J. and Valacich, J. (2015) Essentials of Systems Analysis and
Design. Global Edition. Pearson

19. Hron, M. Obwegeser, N. (2018). Scrum in practice: an overview of Scrum
adaptations. Proceedings of the 2018 51st Hawaii International Conference on System
Sciences (HICSS).
20. Jeff, S. Schwaber, Ken (2013). Scrum Guides. ScrumGuides.org.
21. Johnson, Louise, H. (January 13, 2011). ScrumMaster vs scrum master: What do you
think?. agilelearninglabs.com.
22. Kenneth, K. and Kendall, J. (2013). Systems Analysis and Design. 9th Ed. Pearson
23. Ladas, Corey (2007). scrum-ban. Lean Software Engineering.
24. Larman, C. (2004). Agile and Iterative development. A Managers Guide.
AddisonWesley Professional
25. Leybourn, E. (2013). Directing the Agile Organisation: A Lean Approach to Business
Management. London: IT Governance Publishing: 117–120.
26. Little, Joe (2011). Impediment Management. Agile Consortium.
27. Livermore, J. A. (2007). Factors that Impact Implementing an Agile Software
Development Methodology. in the Proceedings of IEEE.
28. Loukides, Mike (2012). What is DevOps?. O'Reilly_Media.
29. Marakas, J. A. George M. (2010). Management information systems (10th ed.). New
York: McGraw-Hill/Irwin. pp. 485–489
30. Martin, R. (2013). Agile Software Development, Principles, Patterns, and Practice.
New International Edition. Pearson.
31. Maximini, Dominik (January 8, 2015). The Scrum Culture: Introducing Agile Methods in
Organizations. Management for Professionals. Cham: Springer (published 2015). p. 26.
32. Moran, A. (2014). Agile Risk Management. Springer Verlag.
33. Morris, David (2017). Scrum: an ideal framework for agile projects. In Easy Steps.
pp. 178–179
34. N.A. (2012). Issues and Challenges in Scrum Implementation. International Journal of
Scientific & Engineering Research. 3 (8).
35. N.A. (August 2013 ed.). Chapter 5: Institute of Chartered Accountants of India.
Control and Audit, Information Systems. SDLC p. 5.28.
36. Partogi, Joshua (July 7, 2013). Certified Scrum Master vs Professional Scrum Master.
Lean Agile Institute.
37. Pichler, Roman. (2010). Agile Product Management with Scrum: Creating Products that
Customers Love. Upper Saddle River, NJ: Addison-Wesley.
38. Pope-Ruark, Rebecca (2012). We Scrum Every Day: Using Scrum Project Management
Framework for Group Projects. College Teaching.

39. Ramtin, J. Ali, N. and Kai, P. Binish, T. (2016). What is DevOps?: A Systematic
Mapping Study on Definitions and Practices. Proceedings of the 2016 Scientific
Workshop . Association for Computing Machinery
40. Russ J. M. Milosevic, D. Z. (2016). Project Management ToolBox: Tools and Techniques
for the Practicing Project Manager. Wiley
41. Sterling, Chris (2007). Research, Spikes, Tracer Bullets, Oh My!. Getting Agile.
42. Taylor, G.D. (2008). Introduction to Logistics Engineering. CRC Press. pp. 12.6–
12.18.
43. Tobin, J. L. and Sharma, A. (2011). Software Development as a service. Agile
Experiences, in annual SRII Global Conference.
44. Vacaniti, Daniel (2018). The Kanban Guide for Scrum Teams . scrum.org.
45. Vasiliauskas, Vidas (2014). Developing agile project task and team management
practices. Eylean.
46. Verheyen, Gunther (March 21, 2013). Scrum: Framework, not methodology. Gunther
Verheyen. Gunther Verheyen.