Software Developments

Methods and Standards

By:
Assistant Prof.
Dr. Rebwar M. Nabi
Topics covered
 Agile methods
 Plan-driven and agile development
 Extreme programming
 Agile project management
 Scaling agile methods

IT Dept. Technical College of Informartics -

02/15/23 2
SPU
 Rapid software development

 Why?
 Need to react to changes more quickly than 2 year long waterfall projects
 2 years and then you got the design wrong anyway! Small deliveries aren't
abstract
 How?
 Goal - Deliver working software quickly
• Compromise - less functionality in a delivery, not lower quality
• Less documentation
 Focus on the code rather than the design
 Interleave
• Specification, design and implementation are inter-leaved
 Deliver small versions and get user (stakeholder) input

IT Dept. Technical College of Informartics -

02/15/23 3
SPU
Painpoints

Your Favorite!

s
Transparency

es
en
siv
on
Long

sp
Com

Re
Prod

plexi

Cycle
uctiv

ty

e
od
ali
ty

C
Qu
ity

Tim

tle
it
Br
es

02/15/23 IT Dept. Technical College of Informartics - 4

SPU
Agile manifesto
 Our values:
 Individuals and interactions over processes and tools
 Working software over comprehensive documentation
 Customer collaboration over contract negotiation
 Responding to change over following a plan
 That is, while there is value in the items on the right, we
value the items on the left more.

IT Dept. Technical College of Informartics -

02/15/23 5
SPU
Plan-driven and agile specification
separate Iteration within stage
development Not
stages with necessarily
the outputs to waterfall
be produced model – plan-
at each of driven,
these stages incremental
planned in development
advance. is possible

User's full
agreement at
end, not before
code
Iteration of stage

IT Dept. Technical College of Informartics -

02/15/23 6
SPU
02/15/23 IT Dept. Technical College of Informartics - 7
SPU
Problems with agile methods
 It can be difficult to keep the interest of customers / users who are involved
in the process.
 Team members may be unsuited to the intense involvement that
characterizes agile methods.
 Prioritizing changes can be difficult where there are multiple stakeholders.
 Maintaining simplicity requires extra work.
 Contracts may be a problem as with other approaches to iterative
development.
 Because of their focus on small, tightly-integrated teams, there are
problems in scaling agile methods to large systems.
 Less emphasis on documentation - harder to maintain when you get a new
team for maintenance

IT Dept. Technical College of Informartics -

02/15/23 8
SPU
Balance plan driven and agile
 Not great for Agile:
 What type of system is being developed?
• Plan-driven approaches may be required for systems that require a lot of analysis before implementation (e.g. real-time system with
complex timing requirements).
 What is the expected system lifetime?
• Long-lifetime systems may require more design documentation to communicate the original intentions of the system developers to the
support team.
 What technologies are available to support system development?
• Agile methods rely on good tools to keep track of an evolving design
 How is the development team organized?
• Many teams; Outsourcing ---> need design documents to control borders
 Culture or contract needs detailed specification
 Is rapid feedback from users realistic?
 Large scale, not co-located may require more formal communication methods
 Need high level programming skills - refactoring, work with little spec
 Outside regulation documentation requirements

IT Dept. Technical College of Informartics -

02/15/23 9
SPU
Extreme programming
 A popular form of Agile
 Extreme Programming (XP) takes an ‘extreme’ approach to iterative
development.
 New versions may be built several times per day;
 Increments are delivered to customers every 2 weeks;
 All tests must be run for every build and the build is only accepted if tests run
successfully.
 Customer involvement means full-time customer engagement with the team.
- Specifications through user stories broken into tasks
 People not process : pair programming, collective ownership and a process
that avoids long working hours.
 Regular system releases. - release set of user stories
 Maintaining simplicity through constant refactoring of code.

IT Dept. Technical College of Informartics -

02/15/23 10
SPU
The extreme programming release
cycle

IT Dept. Technical College of Informartics -

02/15/23 11
SPU
The Parts and the Whole

• Iteration Plan
• Daily Stand-Up

Set Target Adapt Controller

• Clean Design & Code & Inspect

Refactor
• User Stories - Late Elaboration
• Shared Code Ownership • Pair Programming
• Test Driven Development….. • Customer Reviews &
Feedback
• Retrospectives
Sustainable pace • AutoTest…..
Collective Ownership with users
02/15/23
Minimal documentation for sprint
IT Dept. Technical College of Informartics -
12
SPU
The Life of an Iteration

02/15/23 IT Dept. Technical College of Informartics - 13

SPU
Transparency

“Tell me how you will measure

me and I’ll tell you how I’ll
behave”

02/15/23 IT Dept. Technical College of Informartics - 14

SPU
A ‘prescribing medication’ story

IT Dept. Technical College of Informartics -

02/15/23 15
SPU
Examples of task cards for
prescribing medication

IT Dept. Technical College of Informartics -

02/15/23 16
SPU
 IT Dept. Technical College of Informartics -
02/15/23 17
SPU
Refactoring
 Programming team look for possible software improvements and make
these improvements even where there is no immediate need for them.
 This improves the understandability of the software and so reduces the
need for documentation.
 Changes are easier to make because the code is well-structured and
clear.
 However, some changes requires architecture refactoring and this is
much more expensive.
 RISK:
 Changes the user does not test
 Changes to working software break it

IT Dept. Technical College of Informartics -

02/15/23 18
SPU
Examples of refactoring
 Re-organization of a class hierarchy to remove duplicate
code.
 Tidying up and renaming attributes and methods to
make them easier to understand.
 The replacement of inline code with calls to methods that
have been included in a program library.

IT Dept. Technical College of Informartics -

02/15/23 19
SPU
Test case description for dose
checking

IT Dept. Technical College of Informartics -

02/15/23 20
SPU
Test automation
 Automate tests (junit)
 Run upon checkin
 Difficulties:
 Time constraints
 Programmer preferences to not test
 Test coverage

IT Dept. Technical College of Informartics -

02/15/23 21
SPU
Pair programming
 In XP, programmers work in pairs, sitting together to
develop code.
 Common ownership
 Knowledge spread
 Informal review
 Refactoring
 Similar output to two people coding

IT Dept. Technical College of Informartics -

02/15/23 22
SPU
Scrum
 Project Manager's job: - Deliver needed system on time
within budget
 The Scrum approach - manage the iterations
 There are three phases in Scrum.
 outline planning phase - general picture and architecture
 Sprint cycles releasing increments of the system.
 The project closure phase - final delivery, documentation and
review of lessons learned.

IT Dept. Technical College of Informartics -

02/15/23 23
SPU
The Scrum process

IT Dept. Technical College of Informartics -

02/15/23 24
SPU
The Sprint cycle
 Every 2–4 weeks (a fixed length).
 1) Project team with customer: Look at product backlog -
select stories to implement
 2) implement with all customer communication through
scrum master (protecting pgmr at this point)
 Scrum master has project manager role during sprint
 Daily 15 min meetings
 Stand up often
 Team presents progress and impediments
 Scrum master tasked with removing impediments
 3) Review system release with user
IT Dept. Technical College of Informartics -
02/15/23 25
SPU
Scrum benefits
 The product is broken down into a set of manageable
and understandable chunks.
 Unstable requirements do not hold up progress.
 The whole team have visibility of everything and
consequently team communication is improved.
 Customers see on-time delivery of increments and gain
feedback on how the product works.
 Trust between customers and developers is established
and a positive culture is created in which everyone
expects the project to succeed.

IT Dept. Technical College of Informartics -

02/15/23 26
SPU
Necessary for Every Projects

 S.I.D. User Stories & Standards

 Business Process Models
 Stake Holder Analysis
 Deliverables

IT Dept. Technical College of Informartics -

02/15/23 27
SPU
SHA

IT Dept. Technical College of Informartics -

02/15/23 28
SPU
SHA - 2

IT Dept. Technical College of Informartics -

02/15/23 29
SPU
User Stories

IT Dept. Technical College of Informartics -

02/15/23 30
SPU
System Requirements

1. System Functional Requirements:

 Scalability to add new departments or units to the organization
 Generating electronic forms to process required data.
 Generating electronic reports to retrieve, save and reuse required information.
 Generating automated business workflows to impose a certain sequence of activities leading to the
expected result for the performed task.
 Supporting authorization rules to assign different privileges and access rights to specific users/groups.
 Support accountability mechanisms by deploying detailed logging of system activities.
 Ability to sign / approve official letters and adding explanations (to the margins) electronically
 Implementing multiple factor authentication to enhance system security.
 Perform automated mathematical formulas and functions in different system sections that deploy out
solutions (insurance estimation, auditing, accounting, treasury…etc.).
 Easiness of system using (mostly drag and drop activity) by different directorate officials.
 Save cost by reducing paper usage to almost (zero).
 Save time of S.I.D officials by automating most of business processes.
 Save dossiers’ documents electronically.
 Supporting automatic backup plans (daily, weekly, monthly…etc.)

IT Dept. Technical College of Informartics -

02/15/23 31
SPU
2- System Non-Functional Requirements:

1. Supporting manual backup plans (daily, weekly, monthly…etc.)

2. Support (English and Arabic) languages
3. Friendly interface.
4. Support dynamic form and report generation by system admin and concerning
users.
5. Perform periodical security scan for the specific users and top management
positions.
6. Setting alarms and reminders to a task / activity.
7. Supporting internal messaging feature between system users.
8. Ability to specify the priority of a task for the assigned user.
9. Ability to specify a letter / task sensitivity for the assigned user.
10. Ability to remind a user to finish the assigned task before its appointed date.

IT Dept. Technical College of Informartics -

02/15/23 32
SPU
Summary
 Plan Driven (Ex: Waterfall) vs Incremental (Ex: Agile )
 Structure and benefits and downfalls
 XP - an implementation of Agile - Power to the Programmer
 User story requirements
 Test driven design with continual retest and integration
 Pair Programming
 Refactoring encouraged
 Scrum - project management of Agile using sprints
 Iterations of full team contact / Scrum master protection of
programmers / full team release review

IT Dept. Technical College of Informartics -

02/15/23 33
SPU