Title: Advanced Systems Analysis and Design Process Modelling SOFT 30121 L8
URL Source: blob://pdf/8c404bd1-c884-404c-9881-c31b51ba05b6
Markdown Content:
Advanced Systems Analysis and Design
Moving into Implementation
and Transition to the new system
W8 SOFT 30121
Arshad Sher Learning objectives
Understand how to manage the programming process.
Understand about coding standards.
Understand how to develop user documentation.
Understand the different types of conversion strategies and when to
use them.
> 2
Advanced Systems Analysis and Design
> 3
Planning Analysis Design Implementation
Project management Moving into Implementation
Systems Analysis and Design
Alan Dennis; Barbara Haley Wixom; Roberta M. Roth
2019
Chapter 12 The implementation phase
Doing a thorough job on the analysis and design phases is essential
to a smooth and successful implementation phase
In industry, while programmers/developers are transforming
program specifications into code, the systems analyst is designing
a variety of tests , as well as finalising the system
documentation and user documentation
> 03 May 2025 5
## Managing the programming process
Tasks the project manager must do to manage the programming
effort:
Assigning programming tasks
Coordinating the activities
Managing the programming schedule
> 03 May 2025 6
## Assigning programming tasks
Use cases that are related are grouped together.
These groups are then assigned to programmers on the basis of
their experience and skill
It may be identified here that there is a mismatch between the skills of the
team, and the skills needed to complete the project
Consequently, the project manager must take steps at this time to ensure that
skill deficiencies are eliminated through additional training or through
mentoring arrangements with more experienced, skilled programmers.
The additional time needed for the team members to be trained/mentored
should be considered.
After a point, the more programmers who are involved, the longer
the system will take (as the need for coordination increases)
The project manager may need to account for the extra time needed in the
schedule for training/mentoring.
> 03 May 2025 7
## Coordinating Activities
Communication is key!
Regular, brief meetings encourage the discussion of issues before
they become problems
Often they can be done standing up (referred to as standups )
Standups are simple. Each member of the team answers 3
questions:
What did I work on yesterday?
What am I working on today?
What issues are blocking me?
> 03 May 2025 8
## Managing the schedule
Scope creep can become an issues at this stage. Scope creep
occurs when requirements are added to the project after system
design has been finalised. Any features added at this point should
be carefully considered
Unnoticed day -by -day slippages can cause delays in the schedule.
These minor delays can add up! Communication between the
programming team is important to watch these minor slippages.
> 03 May 2025 9
## Coding Standards
> 03 May 2025 10
## Coding Standards
Used to ensure that your code is good quality.
Makes the software more
> Reliable
> Maintainable
> Secure
> etc.
There are some standards:
CERT Coding Standards
https://en.wikipedia.org/wiki/CERT_Coding_Standards
Offered for various programming languages e.g. Java, C++ Coding standards: static code analysis
Checks the software without executing it
Applies rules to the code (text) to see if it passes or not
> 03 May 2025 12
## Coding standards: automated reviews
SonarQube: Open -source platform for continuous inspection
of code quality
Can perform automatic reviews with static analysis of code to
detect:
Bugs
code smells,
security vulnerabilities
on 20+ programming languages
> 13
code smell is any characteristic in the source code of a program that could
indicate a deeper problem Typical output of automated reviews
> 03 May 2025 14
## Coding Standards: tags in SonarQube Coding Standards
Brain Overload Tag in SonarQube
https://www.sonarsource.com/docs/CognitiveComplexity.pdf IDE support: use Visual Studio to enforce rules Developing documentation
System documentation is intended to help programmers and
systems analysts understand the application software and enable
them to build it or maintain it after the system is installed
Should be created as the project unfolds
This includes code comments, source control log etc.
User documentation (such as user manuals, training manuals,
and online help systems) is designed to help the user operate the
system
Producing documentation requires designing the documents (whether paper or
online), writing the text, editing them, and testing them.
Reviewing documentation
Can your quality control person(s) review the documentation before it is signed
off as completed?
> 03 May 2025 18
## Types of user documentation
Procedures manuals
Describe how to perform business tasks
Guides the user through a task that requires several functions or steps in the
system.
Each entry is typically much longer than an entry in a reference document
Tutorials
Teach people how to use major components of the system
Longer still than the entries in procedures manuals
Reference documents:
are designed to be used when the user needs to learn how to perform a specific
function
Typically read only after the user has tried and failed to perform the function
Requires special care because users are often impatient or frustrated when
they begin to read them
> 03 May 2025 19
Advanced Systems Analysis and Design
Transition to the new system
SOFT 30121
Arshad Sher Advanced Systems Analysis and Design
> 21
Planning Analysis Design Implementation
Project management Transition to the new system
Systems Analysis and Design
Alan Dennis; Barbara Haley Wixom; Roberta M. Roth
2019
Chapter 13 Transition to the new system
Aims:
Turn off the old system
Turn on the new system
Could also be applying major updates to a system
> 03 May 2025 23
## IT system failures
https://www.exoplatform.com/blog/5 -of -the -biggest -information -
technology -failures -and -scares/
When should you update a system?
Ever had problems with Windows updating at an inconvenient time?
A German pro basketball team was relegated to a lower division due
to a Windows update
> 03 May 2025 24
## Selecting a Conversion Strategy
03 May 2025 25
Will all modules within the
system be installed
immediately or not?
What style will be used to
turn on the new system?
What parts (locations) of the
business will get the new
system and when? Direct
An abrupt change is called direct conversion
It involves the instant replacement of the old system with the new
system.
The old system is turned off and the new is turned on
> often coinciding with a fiscal -year change or other calendar event
+
Simple and straightforward way of converting to the new system
-
Any problems with the new system may seriously disrupt the
organizations ability to function
> 03 May 2025 26
## Parallel
A more gradual introduction is made with
parallel conversion
The two systems are operated side by side (for a period in time),
and users must work with both the old and new systems.
+
reduces risk by providing the organization with a fallback
position if major problems are encountered with the new system
-
users are required to do their job tasks twice
> 03 May 2025 27
## Pilot
A pilot conversion selects one or more locations (or units or work
groups within a location) to be converted first as a part of a pilot
test.
If the conversion at the pilot location is successful, then the system
is installed at the remaining locations
+
reduces risk by limiting the effect of the new system to just the pilot
location
-
Takes time to install the system everywhere
> 03 May 2025 28
## Phased
Similar to pilot except that with phased conversion, a first set of
locations is converted, then a second set, then a third set, and so
on, until all locations are converted.
(same as pilot)
+
reduces risk by limiting the effect of the new system to just the pilot
location
-
Takes time to install the system everywhere
> 03 May 2025 29
## Simultaneous
The new system is installed at all locations at once.
+
eliminates the problem of having different organizational units using
different systems and processes
-
there must be sufficient staff to perform the conversion and train
the users at all locations simultaneously
> 03 May 2025 30
## Whole system
Installing the entire system (all modules)
at one time
+
Simple and straightforward and is required if the system consists of
tightly integrated modules.
-
If the system is large and/or extremely complex, however (e.g., an
enterprise resource planning system such as SAP or Oracle), the
whole system may prove too difficult for users to learn in one
conversion step
> 03 May 2025 31
## Module by module
Installing one module at a time.
+
Reduces the amount of training needed for people to begin using
the new system, since users need to be trained only for the new
module being implemented.
-
Requires special care in developing the system (and usually adds
extra cost), because each module must be written to work with both
the old and the new systems.
> 03 May 2025 32
## Evaluating Strategy Choices
> 03 May 2025 33
## Summary
Understand how to manage the programming process.
Understand about coding standards.
Understand how to develop user documentation.
Understand the different types of conversion strategies and when to
use them.
> 34
## Questions