Ingen bildrubrik

1
Tools and Documentation
1 Life Cycle Model 2 And Documentation 3 Info
rmation Management 4 Revision Control 5 Configura
tion Management 6 Tools 7 Assignment
2
System Life Cycle Model
Definition Development Release Use Reti
rement
3
System Life Cycle - Main Activities
Concept Planning Requirements
Preliminary Design Detailed Design Implementation
Unit Testing Integration Validation Testing FAT
System Integration Installation Checkout SAT
Cutover Field Trials FLT Operations Maintenance
Functional Baseline
Product Baseline
System Baseline
Definition
Development
Release
Use
4
Definitions
System Products, environment, users,
HW Product HW or SW to be delivered to
user Code, Manual, box, CD COTS
Commercial Off The Shelf Software Code
plus docs plus all necessities
5
Systems Development
V-model
Contract Reqs
Acceptance Test
FB
SB
PB
Definition Concept-Reqs
Release Validation-Install
Development
Design Prel - Detail
Integration Build-Test
Implement Code - Unit Test
6
Riskfaktorer
Etablera Projektet
Otydlig rollfördelning
Komplexitet, verksamhet
Komplexitet, arkitektur
Höga förväntningar på Övriga krav
Många leverantörer
Ny teknik
Många intressenter
Komplexitet, funktionalitet
Otydlig ansvarsfördelning
Utvecklingen utsträckt i tiden
Lång förväntad driftstid innan avveckling
7
Strategierna...

• Formaliserad avtalsskrivning
• Formaliserad projektledning
• Formaliserad utvecklingsmetodik
• Dokumentera
• Dokumentera
• Dokumentera mera..

8
Documents Why? - To collect information -
To store information - To find information - To
freeze information Documentation is INFORMATION
about something - a certain purpose archived on
a media..
9
Braigheter med dokument

• Projektperspektiv
• Kontroll för samförstånd mellan kund och
  leverantör
• Möjligöra kvalitetssäkringar
• Möjliggöra insyn
• Säkra projektet över tiden
• Säkra nästa utvecklingsomgång
• Organisationsperspektiv
• Vidarebefordra erfarenheter till andra projekt
• Säkra organisationens tillgångar

10
Documents
Documentation is modelling the system for
different purposes Different views of the
system Documentation may be text, online, web,
pictures ..

• Product Documents - Results
• Specifications - requirements/musts
• Descriptions - understanding/explaining/stru
  ctures
• Manuals - how to use, how to fix
• Training Material

• Project Documents
• Plans - activities/resources/times
• Standards and Rules - instructions/coding
  rules/
• Reporting - hours/errors/inspection results

11
Documents
Documents can be Standards ISO,
IEEE, .. Proprietary Ericsson, ABB, ...
IEEE Std No IEEE Documents See also BBook
830 SRS Software Requirements
Specification 1016 SDD Software Design
Description 829 STD Software Test
Documentation 1058 PMP software Project
Management Plan 730 SQAP Software Quality
Assurance Plan 1012 SVVP Software Verification
and Validation Plan 828 SCMP Software
Configuration Management Plan SDP Software
Development Plan
12
Product Development Documents
V-model
STProcedures
Contract Reqs
Acceptance Test
FB
PB
SVTP - Procedures
Validation Test Report
SRS
Allocation
Integration
Build
Test Report
SITP
PSDD -SDD
Code - Unit
Subsystem
13
Project Management Documents
Project Plan
Quality Plan
Software Configuration Management Plan
SVVP
STP
Definition Concept-Reqs
Validation/Acceptance System Test
SDP
Integration Subsystem
Design Prel - Detail
Integration Kit
Integration Kit
Implement Code - Unit test
Implement Code - Unit test
14
Example Project Plan 73-93 Case Study 123 - 131
Projektplanen ska besvara frågor som - Vad ska
utvecklas? - Vilken tidsplan ? Huvudfaser MS? -
Vilken organisation? Vem? Kompetens? - Vilka
leverabler ? Dokument/kod/utrustning.. - Vad
kostar det? - Krav på omgivningen? -
Risker? Detaljerad plan - Vilka delar?
Delsystem/moduler ..? - Vilka aktiviteter? Koda -
testa ? - Resurser per aktivitet? Tid? -
Delleveranser? - Beroenden? - ...
Project Plan
Introduction - Goal
Organization
Milestones and Phases
Activities and Deliverables
Budget Resources
Test Release
Riscs
Projektplanen binder ihop alla projektdelar !!!
15
Information Management
16
Information Management
Formal Info Control
Info about the info?
A piece of info
17
Information Management

• Information management is
• Management of the info content (correctness,
  timeliness,..)
• Mangement of info visibility (publish,
  secrecy, web..)
• Management of understandability (reader, viewer,
  language ..)
• Management of format (size, font, colour, ..)
• Management of searchability (how to find the
  info)

18
Information Management
Info Control
Example

• Metadata
• Information about the document
• Title
• Writer
• Publication Date
• Unique Identity
• Secrecy
• etc
• International agreements, i e Dublin Core
  Metadata
• Company Standards and also part of
• Quality System

19
Exempel på dokumentinfo...
20
Information Management
- How?

• Revision Control
• By time and date? When printed, when created,
  .?
• By state of information (created, published,
  revised)
• By formal numbering like 1.0, 1.1 etc
• By approval

21
Document Life Cycle
Pappersinsamlingen?
22
Information Management
Configuration Management of Documents
Example PA1 ..PA2PA3..
ok
A
Formal Approval Review
PB1 ..PB2PB3..
ok
B
Formal Approval Review
23
"No work is finished until the paperwork is
done!"
24
Versionskontroll
LEVERANS
LEVERANS
Kunder
A
Produkt Ett
B
System- produkt
Produkt Två
Produkt Tre
Konfiguration
Kod
Provfall
Dokumentation
25
CM
PROGRAMVARA
Program, procedurer, regler och tillhörande
specificerande och redovisande dokumentation
KOD
Specifikationer
Granskningsprotokoll
Provprogram
Beskrivningar
Provningsprotokoll
Hjälpprogram
Gränssnittsspecar
Rapporter
Stubbar
Källkod
Felrapporter
Drivers
Provspecar
Statusbeskrivning
Data
Provbeskrivningar
ETC
Scripts
Användardokumentation
Tekniska
Drifts- och
hjälprutiner
operatörsanvisningar
ETC
ETC..
PRODUKT
Programvara som ska levereras till användare
26
The Parts Configuration Software
Component Configuration Software
Unit Configuration Item
Identification ----- Naming? Program
Filename Name_spec Name_body Physical
limits?? Hardware -- Software -- Firmware
27
Information Management
Configuration Management
Document Survey or List of documents SystemX Rele
ase 1.0 System Documentation SRS BaraPratno123
Rev B SDD BaraPratno999 Rev A Users
Guide NoTalk000 Rev A see Quality Plan or SCMP
or ISO9001 Group of documents..
28
Förhållande progr./dok.
1/3
29
PROBLEMS AND CHANGES
30
We have a problem?
OM FEL FINNS HOS FLERA KUNDER ?
FIXA EN ELLER
ALLA?
FIXA NU ELLER SENARE?
OM FEL PÅVERKAR DATABAS ?
KÖRA OM TRANSAKTIONER?
OCH OM FELET FANNS I N-1, N-2, .....?
KRAV FÖR KRITISKA SYSTEM
ALLTID KUNNA ÅTERSKAPA IDENTISKT
SYSTEM FÖR GIVET TILLFÄLLE !
LEVERERAT SYSTEM IDENTISKT MED
PROVAT SYSTEM !
FRUSEN KOMPILATOR !
31
STRATEGI Unik till var och en Skräddarsydd
produkt
LEVERANS
LEVERANS
A
Leverans A
B

System- produkt
Leverans B
Leverans A Systemprodukt v1 bestående av
delprodukterna X.1, Y.3 ...
Leverans B Systemprodukt v2 bestående av
delprodukterna X.2, Y.3 ...
gt total kontroll över vad som levererats till
viss kund
gt höga krav på noggrannhet i felrättning och
ändringar dessa blir unika för
varje leverans
gt vid felsökning/rättning måste vi kunna
återskapa den unika leveransen
32
STRATEGI Samma till alla Konsumentprodukt
stall (uppehåll de som hittar fel)
LEVERANS
LEVERANS
Konfiguration 1
A
Konfiguration 2
B
Produkt
System
Fix
Konfiguration 1 A Systemprodukt version 1
bestående av delprodukterna X.1, Y.3 etc

Fix B Systemprodukt version 1.1 bestående av
delprodukterna X.1, Y.3 ...
med följande fel rättade .... X.11, Y.32 ...
Konfiguration 2 A B
Systemprodukt version 2 bestående av
delprodukterna X.3, Y.3 ...
gt kontroll över konfiguration
gt höga krav på noggrannhet i felrättning och
ändringar dessa blir unika för
varje konfiguration
33
SystemX N1 F E ??
SystemX N F
SystemX N F E
Railtrack N1 F NF E ??
System X
Railtrack System
Modif.
Errors
New Functions
Functions
CoreBaseline
CORE Segment
CORE Segment
version N
N1
34
Change Control
Felrap.
Ändringsbeg.
Change Control Board
Projekt Kund Konstruktion
PH
BESLUT (fel eller
ändring?)
ÅTGÄRD
RÄTTA/ÄNDRA SPARA EJ
35
Change Control
PROGRAM-
ÄNDRINGS-
OMPROVNING
ÄNDRING
BEGÄRAN
FÖRSTÅELSE!???
Korrigering
Förbättring
ÄNDRA
Adaptering
PROVA
PROVA
ÄNDRA
KOD
Preventiv
ÄNDRING
OMGIVNING
DESIGN
Sanering
ÄNDRA
ÄNDRA
äNDRA
DOK.
PROV
SPEC
UTVECKLING
UNDERHÅLL FRÅN
NOLL
36
Change Control Procedure
Ändringshantering
ECP ECR ECN
ÄNDRING
FEL
UTGÅVA N
CCB
UTGÅVA N1
KONSTRUKTION
OK?
PROV
37
Change Control
Delivery Notice   1 OLD FUNCTIONS 2 NEW
FUNCTIONS 3 CHANGED FUNCTIONS 4 ERRORS
CORRECTED 5 KNOWN PROBLEMS CORRECTED 6 NEW KNOWN
PROBLEMS
38
AUDITs and REVIEWs
39
Project Reviews
Reviews
DESIGN
INTEGRERING
ANALYS
KODNING
PROVNING
SRR
PDR
DDR
TRR
TRR
40
CM - Audits
Baselines
Functional Baseline
Product Baseline
System Baseline
Requirements
Coding
Functional
Physical
DESIGN
INTEGRERING
ANALYS
KODNING
PROVNING
Contract Requirements Audit
FCA
PCA
Allocated
-         after FAT as per product
baseline. -         after SAT as per system
baseline -         after Trials as per final
delivery.
41
Audit
EVERYTHING INCLUDED? RÄTT VERSIONER? TESTS
PERFORMED?
Specifikationer
Granskningsprotokoll
Provprogram
Beskrivningar
Provningsprotokoll
Hjälpprogram
Gränssnittsspecar
Rapporter
Stubbar
Källkod
Felrapporter
Drivers
Provspecar
Statusbeskrivning
Data
Provbeskrivningar
ETC
Scripts
Användardokumentation
Tekniska
Drifts- och
hjälprutiner
operatörsanvisningar
ETC
ETC..
42
Configuration Audit

ConfigurationControl

• CCB Control
• Change Management
• Configuring
• Archive Handling

Product
Identification
Baseline Handling

• Versioning
• Numbering
• Product Structuring

Status Accounting
43
Example SCMP - IEEE 828
SCMP
Introduction
SCM Management
SCM Activities
SCM Schedules
SCM Resources
SCM Plan
Other Standards
44
Example SCMP - IEEE 828
SCM Management Organization (linje, projekt,
tekniska och management) Responsibilities (vem
ansvarar för varje SCM aktivitet?) Policies,
Directives and Procedures (yttre/andra krav på
CM) SCM Activities Configuration Identification
(Identifiera - Namnge - Arkiv) Configuration
Control (Begäran - Värdering - Beslut -
Införa) Configuration Status Accounting (Vad -
hur - när - access- rapporter) Configuration
Audits and Reviews (Vad - när - underlag -
kriteria -hur) SCM Schedules Ordning -
koordinering - beroenden - relation till
projektplan SCM Resources Tools, techniques,
training, personnel.. SCM Plan Maintenance Ändrin
gar av SCMP - vem - när - hur ?
45

• Configuration Management System, Intro
• Configuration Management Process
• Configuration Management Organisation
• Configuration Management Procedures
• Configuration Management Plan

46
And SMD136 ???
You and five friends have recently started a
software company. An investor is willing to
invest 6 manyears in the development of the
companys first system. An initial project
portfolio is ordered as a prestudy (equal to 6
manmonths of work). Your task will be to
produce a project portfolio including
requirements specifications, test plans, project
specifications etc etc
47
Assignments
Your starting point is a problem statement with
an idea for a new software a software that
solves this problem, including some guesstimates
on cost, time,value etc. (A1) This problem
statement - concept - shall be refined, detailed
and planned to a level - project portfolio -
that can be used as baseline for start of
development. The issues You need to address to
establish this project portfolio are -
Requirements on the SW product like ( Use
Cases, Functional Requirements, General
Requirements, Constraints etc) (A3) -
Architecture of the Software Product (Design
models, Classes, Patterns used, User Interface
etc) (A4) - Web Project Office and rules
for Revision control of documents and CM (A2)
- Quality issues (Code review, Quality
assurance) (A5) - How to (use) test of the
product (Test Plan, Test Cases) (A6) -
Activity, resource and time plan for the project
(A7) - Project Plan including Statement of
work, Organisation, Activities and Deliverables,
Milestones (A8) And then You shall present
this project portfolio to The sponsor !!!!
48
Ex Real Life Software Life Cycle
supporting
operative
managing
49
Prestudy phase

• Tollgate (TG0) decision to start prestudy
• Requirement engineering
• Interviews of customer and/or product management
• Analysis
• Business case analysis
• Customers
• Competitors
• Costs
• Benefits
• Risks
• Results in a tender or an assignment for a
  feasibility study

50
Feasibility phase

• Tollgate (TG1) decision to start feasibility
  study
• Requirement engineering
• User-interface prototyping, specification, use
  cases, etc
• System design
• Anathomy, architecture, Implementation Proposals
• Simulations using tools or role play
• Project planning
• Risk analysis
• Estimation of size, effort, cost and schedule
• Resources, competence, organization, etc
• Life-cycle model (prototyping, evolutionary,
  waterfall, etc)
• Results in an assignment for an implementation
  project

51
Assignment CM

• Assignment CM
• Set up your teams Website
• Set up CVS to handle your software
• Requirements
• All deliverables shall be visible on your site
• A documented system for revision control of
  documents shall
• be set up
• Rules for using CVS shall be documented

Delivery 23/9
52
A2
Until Monday 23/9
1.Develop the Website
(project office) for your project.
2.The website shall allow access to
deliverables 3.
-working documents
4. -approved documents.
5.Study CVS and use CVS to version control
your Website.
6.Version data (id_tag) for the website shall be
shown on your website.
7.Write a simple CM-plan. This shall include
8. the document
revision control procedure you use
9. the way CVS may be used for
handling SW in your project
10. other info and rules you think is
necessary for the project.
Remember to keep it simple!!!
53
Tools
Tools??CVS SCCS Clear Case
http//cvsbook.red-bean.com/cvsbook.html Lectures/
05/cvspres.ppt
Book Implementing Configuration
Management Fletcher Buckley ISBN 0-8186-7186-6
IEEE Computer Press
54
The End
Thats all folks! Thanks for your
attention! Next time Requirements Questions??