Lecture 1: Software engineering process and requirementswikidyd.iem.pw.edu.pl/attachments/SoftEng/SE1_Lecture1.pdf · Lecture 1: Software engineering process and requirements Problems

Software Engineering by Albert Ambroziewicz

Lecture 1: Software engineering process and requirements

Problems in software engineering projects

Software engineering methodology

Core practices of software engineering

Role of requirements in the software engineering process

S OD a

Pra cownik d ydakty czny

Student

P rzejrzenie plan u zajęć z

za rz ądzanie m o cenami

D odanie spra wdzianu

Modyfikac ja spra wdzianu

Wpro wa dzenie o cen c ząstkowy ch

Z atwierd zenie o cen końcowych

Wp rowadz enie k ry te riów

o blic zania oceny k ońcowej

Sprawd zenie oc en z zajęć

U prawn io ny prac ownik dydaktyczny

Prze jrze nie p la nu z ajęć

«exten d»« extend»

S OD a

Obejrze nie listy s tu dentó w

Potwierdz enie zło żenia inde ksu

Potwierdzenie skreśle nia studenta

P rzejrze nie historii o siągnię ć

s tu denta

D ok onanie re jestracji studenta po

terminie

Obe jrzenie lis ty studentów przez

D zieka na

P otwie rdzenie wyda nia in deksu

Dokonanie zmiany rejes tra cji s tu denta

Przydzielenie s tu dentó w d o grup

Dziekan

P racownik d zie kanatu Obejrzen ie listy

studentó w p rzez pracownika dziek anatu

«e xtend»

«e xte nd»

«i nc lu de»« exten d»

«exten d»

«exten d»« extend »

«i ncl ud e»«exten d»

36

5 2

1 712 10

811

913

4 1817

151614

Jaka ś zm iana wyma gani.Bard zo i stotn a zm iana wyma gani a

Jakaś zmia na wy maga ni.Bardzo ist otna zmia na wymaga nia

Jakaś zmi ana w ymag ani.Bardz o is totna zmi ana wymag ania

Jaka ś zmi ana wymag ani.Bard zo is totn a zmi ana wyma gania

UżytkownikZamawiający

1 2 3

Analityk wymagań

Software Engineering Slide 1.2 A. Ambroziewicz, M. Śmiałek

What is Software Engineering?

Software engineering (SE) is the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software.

-- IEEE definition


Complexity of software engineering

„Computer programming is definitely the most complicated intellectual task ever performed by the humans. Ever.”

Gerald M. Weinberg – „Understanding the professional programmer”, 1988

The problem: Code contains hundreds of thousands of lines (for average

commercial systems) Code instructions grouped in procedures; the code still contains

thousands of procedures Procedures grouped in modules (classes, components); the code

contains hundreds of modules


Software engineering isn’t only about coding!

Zamawiający Programista

Środowisko

Model środowiska

Kod

Model kodu

Environment Code

Client Programmer

Environment model Code model


What is software engineering about?

Software engineering is about managing complexity Complexity of the client’s needs Complexity of code

Software engineering is about delivering what the client really wants

Software engineering is about organizing teamwork Small teams (2-6 people) Large teams (tens of people) Separated teams (eg. overseas development)


Software engineering projects – success criteria

The project is within its budget The project is within its time limit (deadline) The system delivered fulfils the real needs of the customer

Software engineering project

These are my needs

This is a system fulfilling your

needs


Software engineering “crisis”?

Standish Group, Chaos Report, 2004 34% - software projects

ended with a success 82% - average budget/cost

overrun 52% - average of fulfilled

requirements

First NATO conference on software engineering (1967): “there is a crisis”

Roger Pressman: „it is a chronic affliction”

0%

20%

40%

60%

80%

100%

1994 2004

Sukces Porażka ZagrożoneSuccess Failure Affected


Typical symptoms of the chronic affliction

Unsatisfied clients “this is not the system we meant originally!” “none of our clerks will be able to use it!”

Unsatisfied suppliers “so, what do they want from us?” “why do they change their mind all the time?” “but we have done such a hard work!”

Quarrels about the scope “you want us to build a system twice as large as specified in the

contract!” “but these functions were to be delivered only in the next version!” “you did not deliver the functionality stated in paragraph 24 point 5a

of the contract!” – “oh, yes, we did!”


Typical symptoms of the chronic affliction (cntd.)Chaotic management of changing requirements “hey, guys, add just a little tiny table in the middle of this window, it

will cost you almost nothing” “we thought that this change will not be important for you at all…”

Programmers working 24/7 “we want a pizza at midnight and a lot of Jolt Cola!” “we want ten more programmers!”

Stress at the end of the project “this system works like a snail!” “but we didn’t yet deliver half of the functionality!”

No repeatability of the development process “so, how much will we overrun the budget this time?” “so, how will we write the requirements specification this time?”


Causes of the affliction

Imprecise software specifications “does ‘account’ mean a ‘user account’ or a ‘banking account’?”

Bad communication “oh, so this form is so important…”

Lack of proper architecture “so, what machine will we install this printer subsystem on?”

No management of the system’s complexity “our database has 1500 tables and 2000 classes!”

Very late discovery of serious ambiguities “and only now you tell me that this procedure hasn’t got parameter

X!”


Causes of the affliction (cntd.)

Insufficient testing “it seems that it works…”

Subjective judgements “this specification is quite good…”

No change management “so, why is this form that important?”

Not using CASE tools “we only need a good compiler with an IDE!”

Too late verification of the client’s needs “you should have asked us earlier what colour should the screens

have!”


Cure for the affliction (1)

Jim Johnson, Standish Group: It is getting better (see the statistics), but why? People (software development organizations) start using systematic

processes!

So, what do we need?

meth·od·ol·o·gy [meth-uh-dol-uh-jee]

A set or system of methods, principles, and rules for regulating a given discipline, as in the arts or sciences.

(Random House Unabridged Dictionary 2006)

Methodology!


Cure for the affliction (2)

Software development methodology: Notation – a modelling language to denote all the software

development products (leading to code) Techniques – a description of activities that produce the software

development products (written with the notation) Technical process – ordering of activities into a coherent flow of

work that produces the final software system


Notation for requirements modellingThe notation should reduce complexity of requirements

The notation should be easilytransformable into design and then – code

What should we produce with the notation? models that describe the complex user needs models that allow for managing complex

dependencies between these needs models that are understandable by the users (a

picture is worth more than a thousand words) models that can be later used by the architects

to design the system

What language allows for producing such models?

Unified Modelling Language

Methodology!


Notation reduces complexity

UML allows for realizing abstraction – capability of concentrating on the most important elements; constructing general notions on the basis of detailed ones

Town

House

Window

PublicUtility

Building


Modelling reduces complexity

Model 1.a representation, generally in miniature, to show the construction or appearance of something

2.a simplified representation of a system or phenomenon, as in the sciences or economics, with any hypotheses required to describe the system or explain the phenomenon, often mathematically.


Techniques for requirements elicitation and specification

Analysing the documents Reading documents supplied by

the client to discover the real needs Underlining nouns, verbs Identifying paragraphs of text as requirements

Working one-to-one Interviews with he clients and with the users Apprenticeship (the tutor and his/her student)

Group work Group requirements modelling sessions: users, analysts discover

requirements and write them down in a chosen visual notation Brainstorms

Methodology!


Technical process and requirements (1)

Waterfall lifecycle All the activities lead from the initial user

needs to the final system in “one go”Methodology!

Requirements

Implementation

Design

Verification

Maintenance


Technical process and requirements (2)

Iterative lifecycle Activities are repeated in several smaller cycles to reach the final system in several increments

Methodology!

Initialplanning

Requirements

Analysis

ImplementationClient

pays Validation

Design


severaltimes

Practice 1 – Organize activities of your lifecycle : waterfall vs. iterative

User’s business needs

User Requirements Phase

System Requirements Phase

Architectural Design Phase

Detailed Design Phase

Transfer Phase

SRP

ADP

DDP

TP

Delivered system

?


Waterfall vs. Iterative (1)


Waterfall vs. Iterative (2)


Which technical process is better?

Waterfall Organizes all the activities into “analysis” and “synthesis” – in accordance to

how humans solve problems Allows for easy resource management (analysts, architects, etc.) Gives a clear path from the “beginning” to the “end” BUT: hides all the problems until the very end of the project! Very risky –

that’s why many projects overrun the deadline and budget! BUT: every change in requirements causes chaos!

Iterative Significantly reduces the risk because problems are uncovered after every

iteration Allows for managing change in a very natural way Allows the user to discover the real needs – produces better systems Allows the development team to “learn” the project That’s why many projects succeed – they use iterative lifecycle BUT: is more complicated, can cause significant overhead


Technical process - the hybrid

Spiral lifecycle Hybrid: Activities are repeated to reach the final system in several prototypes (prototyping-in-stages)

Intended for large, expensive and complicated projects.

Methodology!


Technical process and requirements

Requirements in the software lifecycle

Possibility 1: all the requirements gathered before we start developing the system (waterfall)

Possibility 2: scope of the system determined before we start developing the system, detailed requirements determined during development (formal iterative)

Possibility 3: vision of the system determined before we start developing the system, all requirements determined during development (agile)

Methodology!


Why are requirements so important?


Why is methodology so important?


Methodology, how does it work?

?

Notation

TechniquesTechnical process


Software engineering methodologies

Formal methods:

based on assumption that performing appropriate mathematical analyses can contribute to the reliability and robustness of a design

aim at detailed documentation of each step of a development process

Agile methods :

encourage frequent inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and accountability

aim at rapid delivery of high-quality software, and a business approach that aligns development with customer needs and company goals

99% of the projects I've seen come from a Formal background and implement Agile practices incrementally

--- Roy Osherove


Software engineering methodologies

Formal methods: IBM: Rational Unified Process (RUP) Borland: Application Lifecycle Management (ALM) Microsoft: Microsoft Solution Framework (MSF) Eiffel Software: Eiffel Development Framework OPEN Consortium: O-O Process Environ. and Notation (OPEN) OMG: Model-Driven Architecture (MDA) – not a full methodology

Agile methods – Agile Alliance: Kent Beck: eXtreme Programming (XP) DSDM Consortium: Dynamic Systems Dev. Method Alistair Cockburn: Crystal Jim Highsmith: Agile Project Management Scott Ambler: Agile Modeling (AM) – not a full methodology

http://www.omg.org/mda


Software engineering methodologies (cntd.)

Methodologies defined as standards European Space Agency (ESA): PSS-05-0 (ESA Software

Engineering Standards, older standard), ECSS-E-40 (Space Engineering: Software, current standard)

US Department of Defense (DoD): MIL-STD-498 (Software Development and Documentation)

International Standards Organization (ISO): ISO/IEC 12207 (Software Lifecycle Processes)

These standards define mostly the lifecycle process and documentation. No definition of modelling notation or techniques. This means that they are not full methodologies.


Best practices found in methodologies

Technical process: Practice 1: Organize activities of your lifecycle – otherwise you will

have an organizational chaos

Notation: Practice 2: Document all your decisions – otherwise you will quickly

forget why you did what you did

Techniques: Practice 3: Manage requirements – otherwise you will lose the goal Practice 4: Manage change – otherwise you will be overwhelmed

with new “system features” Practice 5: Manage quality – otherwise you will have a dissatisfied

client Practice 6: Manage complexity of the system – otherwise you will

produce a bowl of spaghetti


severaltimes

Practice 1 – Organize activities of your lifecycle : waterfall vs. iterative


User Requirements Phase

System Requirements Phase

Architectural Design Phase

Detailed Design Phase

Transfer Phase

SRP

ADP

DDP

TP

Delivered system

?


Practice 2 – Document all your decisions : commented code vs. documents vs. models

Requirementsdocumentation----------------------------------------------------------------------------------------------------------------------------

Architecturaldocumentation----------------------------------------------------------------------------------------------------------------------------

Codedocumentation----------------------------------------------------------------------------------------------------------------------------

Requirementsmodel

cd Diagram klas

Samoch ód

Właśc iciel

Dowó d Rej estracyj ny

wsp ółwł asno ść

udoku mentowa nie

przynależ noś ć

własn ość

ud Dia gr am przypadk ów użyc ia

S y ste m ,, Pr z y ja zn y W y d z ia ł K o m un ika c ji "

Rejes tr ator

Właśc ic ie l

Zare jes tr ow anie w ydania dow odu re jes tr acyjnego

Zgłosze nie chęc i re jes tra c ji samoc hodu

Zgłos zenie zapot rze bow ania na dow ód re jes tra cyjny

Spra w dzenie stanu re je stra cji

ad D ia gra m c zynnoś ci

Roz po cz ęc ie rej estra cj i

Za końc z eni e re jest rac ji

Reje stra tor po daje nazw isk o do reje stra cji.

Syste m w yszukuje w ła ści cie la o podanym nazw is ku.

c z y zn ale zn ion o?

System re je struje s amoc hód zna lezion ego w ła ści cie la.

Syste m pow iadamia rejes tratora o zareje strow a niu sa mocho du.

Syste m pow ia damia rejes trato ra o nie znal ezieniu w ła ści cie la.

[nie ][t ak]


Code------------------------------------------------

Commentsin code

Architecturalmodel

dd Diagram wdrożenia

stacja_pc

« j ar»R eje stracj a . ja r

serwer_aplikacyjny

serw er_bazy_danych

« SQL db »DB Acce ss.d b

« j a r»Wyd zi a l . ja r

«j a r»Sta tystyki . ja r

id Diagra m kom ponen tów

Aplik acjaR ejestra cji

DaneOsob oweIOsoby

DaneR ejestr acji

IRejestrac ja IStaty styki

Utrwalan ieDany chIDane

ad Diagram czynności

Rozpoc zęci e rejes trac ji

Zakońc zenie rejes tracj i

Rejestrator podaje nazwisko do rejestracji.

System wyszukuje właściciela o podanym nazwisku.

czy z nale z niono ?

System rejestruje samochód znalezionego właściciela.

System powiadamia rejestratora o zarejestrowaniu samochodu.

System powiadamia rejestratora o nieznalezieniu właściciela.

[nie][tak]

sd Diagram sekwencj i

:Rejes tra tor

:Właściciel s :Samochódapl :GUI znaleziony:Właściciel

loop znajdź

[ porówn aj_da ne=fa lse ]

z are jes truj_s a mochód(n azwis ko)

b oolea n:=p orówna j_dan e(naz wis ko)

za zna cz _rejes tra cję ()

rej estruj()

Codemodel

sd Diagram sekwencj i

:Rejes trat or

:Właściciel s :Samochódapl :GUI znaleziony:Właściciel

loop znajdź

[p orównaj _dane =fals e]

z arej estruj_s am och ód(na zwis ko)

boo lean: =por ównaj_d ane(n azwis ko)

z az nacz_re jes trację()

re jes truj()


stacja_pc

« j ar»R eje stracj a . ja r

serwer_aplikacyjny

serw er_bazy_danych

« SQL db »DB Acce ss.d b

« j a r»Wyd zi a l . ja r

«j a r»Sta tystyki . ja r

ad Diagram czynności

Rozpoc zęci e rejes trac ji

Zakońc zenie rejes tracj i

Rejestrator podaje nazwisko do rejestracji.

System wyszukuje właściciela o podanym nazwisku.

czy z nale z niono ?

System rejestruje samochód znalezionego właściciela.

System powiadamia rejestratora o zarejestrowaniu samochodu.

System powiadamia rejestratora o nieznalezieniu właściciela.

[nie][tak]



DaneOsob oweIOsoby

DaneR ejestr acji




Which notation is better?

Commented code Very good practice – allows us and other programmers to maintain

code in the future BUT: documents only local decisions within individual procedures

and modules

Documents Can be written according to standards (templates) No special tools needed (word processor) BUT: tend to become out of date (people don’t like documenting…) BUT: hard to manage dependencies between documents

Models Visual notation is superior over text – map vs. words! Code can be generated semi-automatically from models BUT: needs special tools (CASE tools)


Model as a map

Code or requirements can be better understood if described with a “map”.

Visual notation allows for making the modelled domain simpler.

package pwum l.diagram management ;public class Dia gramWindow extend s JInternalFra me

implem ents InternalFr ameLi stener {protect ed DiagramID diagra mID;protect ed DiagramCanv as diagra mCanv as;protect ed JScrollPane diagra mScro llPan e;

public Diag ramWi ndow( DiagramID diag ramID ) {supe r();this .diagramI D= diagram ID;init ();

}

protect ed void init() {Diag ramData diagra mData = loa dDia gramD ata ();setT itle ( dia gramD ata.g etDiagram Name () );setC losable(t rue);setM aximizabl e(true );setI conifiabl e(true );setR esizable( true);diag ramCanvas = new Diag ramCa nvas(diag ramID );diag ramScroll Pane= new JScro llPa ne(di agram Canvas);setC ontentPan e(diagramS croll Pane );setL ocation(2 10,10);setS ize(Setti ngs.APPLIC ATION _WINDOW_X _SIZE /2, Setti ngs. APPLICATIO N_WINDOW_Y _SIZ E /2) ;JDes ktopPane worki ngSpa ce= Regis try.g etWor kingSpace ();if (work ingSp ace== null) EL.r epor t(EL. INTER NAL_ERROR , thi s, "Workin g spa ce not se t.");work ingSpace. add(this , Setti ngs. DIAGR AM_WI NDOW_LAYER );setV isible(tr ue);show ();addI nternalFr ameListene r(thi s);

}

protect ed void create ToolB ar() {Tool Bar toolBar= Regist ry.ge tToo lBar ();tool Bar.clear ToolBar ();tool Bar.setDi agramCanva s(dia gramCanva s );load DiagramDa ta().setup ToolB ar();

}}

package pwuml.diagrammanagement;

import java.awt.*;import java.awt.event.*;import java.util.*;import javax.swing .*;import javax.swing.event.*;

import pwuml.data.datastorage.*;import pwuml.data.diagram.*;import pwuml.data.base.*;import pwuml.error.*;import pwuml.*;

/*** Implements diagram window, creates diagram's toolbar.** @author david*/

public class DiagramWindow extends JInternalFrameimplements InternalFrameListener {

/*** ID of the diagram which is supposed to be displayed in this

window.*/

protected DiagramID diagramID;protected DiagramCanvas diagramCanvas;protected JScrollPane diagramScrollPane;

public DiagramWindow(DiagramID diagramID) {super();this.diagramID= diagramID;init();

}

protected void init() {DiagramData diagramData= loadDiagramData();setTitle( diagramData.getDiagramName() );setClosable(true);setMaximizable(true);

setIconifiable(true);setResizable(true);diagramCanvas= new DiagramCanvas(diagramID);diagramScrollPane= new JScrollPane(diagramCanvas);setContentPane(diagramScrollPane);setLocation(210,10);setSize(Settings.APPLICATION_WINDOW_X_SIZE /2,

Settings.APPLICATION_WINDOW_Y_SIZE /2);JDesktopPane workingSpace= Registry.getWorkingSpace();if (workingSpace==null) EL.report(EL.INTERNAL_ERROR, this,

"Working space not set.");workingSpace.add(this, Settings.DIAGRAM_WINDOW_LAYER);setVisible(true);show();addInternalFrameListener(this);

}

public DiagramID getDiagramID() {return diagramID;

}

public void setZoom(double newZoomRatio) {diagramCanvas.setZoom(newZoomRatio);

}

public double getZoom() {return diagramCanvas.getZoom();

}

protected DiagramData loadDiagramData() {try {

return (DiagramData) Registry.getDataTransfer().get(diagramID);

} catch (DataObjectNotExistException e) {EL.report(EL.INTERNAL_ERROR, this, "Can't find Diagram

data @ " + diagramID.toString(), e);}return null;

}

protected void createToolBar() {ToolBar toolBar= Registry.getToolBar();toolBar.clearToolBar();toolBar.setDiagramCanvas(diagramCanvas);loadDiagramData().setupToolBar();

}

public DiagramCanvas getDiagramCanvas() {return diagramCanvas;

}

public void internalFrameClosing(InternalFrameEvent e) {// calls deactivation too

}

public void internalFrameClosed(InternalFrameEvent e) {Registry.getDiagramActivation().markDiagramAsClosed(this);

}

public void internalFrameOpened(InternalFrameEvent e) {}

public void internalFrameIconified(InternalFrameEvent e) {}

public void internalFrameDeiconified(InternalFrameEvent e) {}

public void internalFrameActivated(InternalFrameEvent e) {Registry.getDiagramActivation().openDiagram(diagramID);

}

public void internalFrameDeactivated(InternalFrameEvent e) {

Registry.getDiagramActivation().deactivateDiagramWindow(this);}

}

package pwuml.ele ments. nodes .classes;

import ja va.a wt.*;import ja va.a wt.geo m.*;import ja va.uti l.*;

import pwuml. *;import pwuml. error. *;import pwuml. data.b ase.* ;import pwuml. data.d atastorage . *;import pwuml. data.d iagram.Dia gramI D;import pwuml. graphicbase .*;import pwuml. diagrammanagem ent.*;import pwuml. diagrammanagem ent.graphicedition.*;

/***** @author da vid*/publicclass ClassApperance extends GraphicNode {

/*** ID of Class obje ct which contains class data.*/ClassDataID classID;

protected int posX;protected int posY;

protected int width;protected int height;

transient ClassData classData;MethodRen derer metho dRend erer;

protected boolean fullName= false;protected boolean showAttributes= true;protected boolean showMethods= true;

static int MINIMAL_WIDT H; // we will ev aluate it after "em pty" class is createdstatic int MINIMAL_HEIG HT;

final static int FIE LD_ALIGN_ LEFT = 0;final static int FIE LD_ALIGN_ CENTER = 1;final static int LE FT_MARGIN = 10;final static int VERTICAL_SPACE = 4;int y Pointer;

boolean sizeFound = false;

public ClassApperance(ClassApperanceID newObjectID, DiagramID diagramID , ClassDataI D classID) {

super((Gra phicN odeID )newO bjectID, diagramI D);this.classID= classID;addMaster(classID);

meth odRe nderer = new MethodRen derer();loadData() ;setSize();

MINIMAL_WIDTH= width;MINIMAL_HEIGH T= he ight;

}

void loadData() {

try {DataTransfer dt= Re gistry.getD ataTransfer( );classData= (ClassDa ta) dt.get(cl assID);

} catch (DataObjectNotExistExcept ion ex ) {EL .report(EL.I NTER NAL_ERROR , this, "Class does n't exist with ID " + classID.to String( ), ex) ;

}}

public DataObjectID getDataI nstanceID() {

return classID;}

protected vo id reloadAdditionalData( ) {

loadData() ;}

void resetFieldAddition() {

yPointer= posY;}

void a ddField(Graphics g, Stringtext , Font font, int align) {

g.set Font( font);FontMetrics metrics = g.getF ontMetrics() ;int textWidth= metrics.stringWidth(text);int textHeight= metrics.getHeight();

int textX;int textY= yPointer + VERTICAL_SPACE + metrics.getAscent();

if (align== FIEL D_ALIGN_LE FT) textX= posX + LEFT _MARGIN;else textX= (int) ( posX + (width- textWidth)/2 );

g.drawString(tex t, textX, textY);yPointer+ = textHeight + VERTICAL_SPACE;

}

void a ddFieldSepa rator(Graphics g) {

yPointer+ = VERTICAL_SPACE;g.drawLine( posX, yPointer, posX+ width, yPointer);

}

/*** Eval uates width and height so all fields a re visible.*/void setSize() {

height= 0;width= 0;

FontMetrics dataMetrics = Registry.getD ataFon tMetrics();FontMetrics titleMetrics = Registry.getTitleFont Metrics();int textWidth;int textHeight;

// titletextWidth = titleMetrics.stringWidth(classData. name );textHeight = titleMetrics.getHeight();height += VERTI CAL_SPACE + textHeight;if (width<textWidth) width= textWidth;

// title- attributesseparatorheight+= VERTI CAL_SPACE;

textHeight = dataMetrics.getHeight();

// attributesif (showAttributes)

for (int i=0;i<classData.attributes.size( );i++ ) {

AttributeData att= ( AttributeData) classData.attributes. get(i);Stringa ttributeNam e= att.toString();

textWidth= dataMe trics. stringWidth(attributeNam e ) + L EFT_MARGIN;if (width<text Width) width= textWidth;height+ = VERTICAL_SPACE + textHeight;

}

// attributes- methods separatorheight+= VERTI CAL_SPACE;

// m ethods/*g.set Font( Settings.dat aFont );metrics = g.getF ontMetrics() ;textHeight = me trics.getHeight();*/

if (showMethods)for (int i=0;i<classData.met hods.size();i ++) {

MethodData m et= ( MethodData) classData. methods.get (i);String me thodName = methodRe nderer.rend erMethod(m et);textWidth= dataMetrics.stringWidth(method Name) + LEFT_MARGIN;if ( width<text Width) width= textWidth;height+ = VERTICAL_SPACE + textHeight;

}

height+= VERTI CAL_SPACE;width+= 1 0;

sizeFound= true;}

void paintInside (Grap hics g) {

rese tFieldAdd ition ();addF ield(g, classD ata.n ame, Sett ings.title Font, FIEL D_AL IGN_C ENTER );addF ieldSepar ator(g );

if (show Attri butes )for ( int i=0;i< class Data.attr ibute s.siz e();i ++) {

Attribu teDat a att = (Attrib uteData) classD ata.a ttributes .get(i );String attri buteN ame= att. toString ();

addFiel d(g , attri buteN ame, Sett ings.dataF ont, FIEL D_ALIGN_LE FT);}

addF ieldSepar ator(g );if (show Metho ds)

for ( int i=0;i< class Data.meth ods.s ize() ;i++) {

MethodD ata met= ( Metho dData ) classData.me thods.get (i);String metho dName = met hodR enderer.re nderMethod (met );

addFiel d(g , metho dName , Settings.dat aFont , FIE LD_A LIGN_LEFT) ;}

}

Rectangle oldClipBoun ds= null;

public void setSafeCl ip(Gr aphic s g, int x, int y, int width , int heig ht) {

oldC lipBounds = g.getCli pBoun ds();g.cl ipRect(x , y, width , heig ht);

}

public void restoreSa feCli p(Gra phic s g) {

//if (oldClip Bound s==null) retur n;g.se tClip(old ClipBounds );oldC lipBounds = null;

}

public void paint(Gra phics g) {

g.se tColor(Se ttings.NOR MAL_C OLOR );

// draw just in boundssetS afeClip(g , posX, posY, w idth +1, height +1);

g.dr awRect( posX, posY, widt h, height );pain tInside(g );

rest oreSafeCl ip(g);}

public void paintSele cted( Graph ics g) {

g.se tColor(Se ttings.SEL ECTED _COLOR );




public void paintOutl ine(G raphi cs g) {

g.se tColor(Se ttings.SEL ECTED _COLOR );g.dr awRect( posX, posY, widt h, height );

}

public void paintEdit ed(Gr aphic s g) {

g.se tColor(Se ttings.SEL ECTED _COLOR );




public bool ean contai ns(Po int point ) {

retu rn getBounds() .cont ains( poin t);}

public Rect angle getB ounds () {

retu rn new Rectang le(po sX, posY, widt h, height);}

public void move(int vecto rX, int vectorY ) {

posX += vectorX;posY += vectorY;

}

public void graphicEd ition End() {}

public Coll ectio n generate GEPs() {

Arra yList result = new ArrayL ist();resu lt.add(ne w ClassGEP (this , new Poi nt(posX+wi dth, posY +heig ht) ) );retu rn result ;

}

public void formEditi on() {

// this will chang e class data & appe rance (OK) or not ( Cance l)Clas sEdition ce= new ClassEd ition(thi s, classDa ta);

if (ce.d ataCh anged ()) setSiz e();

// updat e datatry {

Reg istry .getD ataTransfe r(). updat e(thi s );Reg istry .getD ataTransfe r(). updat e(cla ssData );

} catch (DataObjec tNotE xistE xcep tion ex) {EL. repor t(EL. INTERNAL_E RROR , thi s, "Class doesn 't exist with ID " + classID .toSt ring(), ex );

}

Diag ramCanvas .updateDep enden tLinks(th is.getID ());Regi stry.getD iagramActi vatio n().refre shAllDiagr amWin dows ();

}

public bool ean hasFor mEdit ion() {

retu rn true;}

}

class ClassG EP extends Standart GEP {

public Clas sGEP( Graph icObject clien tObject, P oint posit ion ) {

supe r(clientO bject , position );}

public void move(Poin t newPosit ion ) {

Clas sApperanc e node= (ClassA pperance) clien tObje ct;

Poin t oldPosi tion= getP ositi on();int newG epX = (int)oldP ositi on.getX ();int newG epY = (int)oldP ositi on.getY ();

int curr entX = (int)new Posit ion.getX ();int curr entY = (int)new Posit ion.getY ();

node .width= curren tX- node.posX ;if (node .widt h<nod e.MINIMAL_ WIDT H) node.width= node. MINI MAL_WIDTH ;newG epX= node.posX + node.wi dth;

node .height = curre ntY- node.posY ;if (node .heig ht<no de.MINIMAL _HEI GHT ) node. heigh t= node.M INIMAL_HEI GHT ;newG epY= node.posY + node.he ight ;

upda teOwnPosi tion(new Point( newGepX , newGe pY));}

}

package pwuml.ele ments. nodes .classes ;

import ja va.a wt.*;import ja va.a wt.geom.*;import ja va.uti l.*;

import pwuml.*;import pwuml.error. *;import pwuml.data.b ase.* ;import pwuml.data.d atastorage. *;import pwuml.data.d iagram.Dia gramI D;import pwuml.graphicbase .*;import pwuml.diagramma nagem ent.*;import pwuml.diagramma nagem ent.graphicedition.*;

/***** @authorda vid*/public class Cla ssApperance exte nds GraphicNode {

/*** ID of Class obje ct which contains class data.*/ClassD ataID classID;

protectedint posX;protectedint posY;

protectedint width;protectedint height;

transient ClassData classData;MethodRen derer metho dRend erer;

protectedboolean fullName= false;protectedboolean showAttributes= true;protectedboolean showMethods= true;

static int MINIMAL_WIDTH; // we will evaluate it after "em pty" class is createdstatic int MINIMAL_HEIG HT;

final static int FIE LD_ALIGN_LEFT = 0;final static int FIE LD_ALIGN_CENTER = 1;final static int LE FT_MARGIN = 10;final static int VERTICAL_SPACE = 4;int yPointer;

boole an sizeFound = false;

public ClassApperance(ClassApperanceID newObjectID, DiagramI D diagramID , ClassDataI D classID) {

super((Gra phicNodeID )newO bjectID, diagramI D);this.classID = classID;addMaster(classID);

meth odRe nderer= new MethodRen derer ();loadData();setSize();

MINIMAL_WIDTH= width;MINIMAL_HEIGHT= he ight;

}

void loadData() {

try {DataTransfer dt= Re gistry.getD ataTransfer();classData= (ClassDa ta) dt.get(cl assID);

} catch (DataObjectNotExistException ex ) {EL .report(EL.I NTER NAL_ERROR , this, "Class does n't exist with ID " + classID.to String(), ex) ;

}}


return classID;}

protectedvoid reloadAdditiona lData ( ) {

loadData() ;}


yPointer= posY;}

void a ddField(Gra phicsg, String text, Font font, intalign) {

g.set Font(f ont);FontMetricsmetrics = g.getF ontMetrics() ;int textWidth= metrics.stringWidth(text);int textHeight= metrics.getHeight();

int textX;int textY= yPointer + VERTIC AL_SPACE + metrics.getAscent();

if (ali gn== FIEL D_ALIGN_LE FT ) textX= posX + LEFT _MARGIN;else textX= (int) ( posX + (width- textWidth)/2 );

g.drawString(text, textX, textY);yPointer+ = textHeight + VERTICAL_SPACE;

}

void a ddFieldSepa rator(Graphi cs g) {

yPointer+ = VER TICAL_SPACE;g.drawLine( posX, yPointer, posX+width, yPointer);

}

/*** Eval uates width and height so all fields a re visi ble.*/void setSize() {

height= 0;width= 0;

FontMetricsdataMetrics = Re gistry.getDataFon tMetrics();FontMetricstitleMetrics = Re gistry.getTitl eFontMetrics();int textWidth;int textHeight;

// titletextWidth= titleMetrics.stringWidth(classData. name );textHeight = titleMetrics.get Height ();height += VERTI CAL_SPACE + textHeight;if (width<textWidth) width= textWidth;

// title- attributes separatorheight+= VERTICAL_SPACE;



for (int i= 0;i<classDa ta.attributes.size( );i++ ) {

AttributeData att= ( AttributeData) classData.attributes. get(i);StringattributeNam e= att.toString();

textWidth= dataMe trics.stringWidth(a ttributeNam e) + L EFT_ MARGIN;if (width<text Width) width= textWidth;height+ = VERTICAL_SPACE + textHei ght;

}

// attributes- methods separatorheight+= VERTICAL_SPACE;

// m ethods/*g.set Font(Settings.dat aFont );metrics= g.getFontMetrics() ;textHeight = me trics.getHeight();*/

if (showMethods)for (int i=0;i<classData.met hods.size(); i++) {

MethodData met= ( MethodData) classData.metho ds.get (i);StringmethodName = meth odRe nderer.rend erMethod(m et);textWidth= dataMetrics.stringWidth(m ethodName) + LE FT_MARGIN;if ( width<textWidth) width= textWidth;height+ = VERTICAL_SPACE + textHeight;

}

height+= VERTICAL_SPACE;width+= 10;

sizeFound = true;}

void paintIn side (Grap hics g) {

rese tFie ldAddition ();addF ield (g, classD ata.n ame , Settings. titleFont , FIELD_AL IGN_C ENTER );addF ield Separator( g);

if (show Attri butes )for ( int i=0;i< class Data. attribute s.siz e();i ++) {

Attribu teData att = (Attrib uteDa ta) classD ata.a ttri butes.get( i);String attri buteN ame = att.toStr ing();

addFiel d(g, attributeN ame, Sett ings. dataFont , FIEL D_ALI GN_LEFT);}

addF ield Separator( g);if (show Metho ds)

for ( int i=0;i< class Data. methods.s ize() ;i++) {

MethodD ata met= ( MethodDat a) classDa ta.methods .get (i);String metho dName = methodR ender er.renderM ethod(met );

addFiel d(g, methodName , Setting s.dataFont , FIE LD_A LIGN_ LEFT);}

}

Rectang le oldCli pBounds = null;

public void setS afeClip(Gr aphic s g, int x, int y, int width , int heig ht) {

oldC lipB ounds = g.g etClipBoun ds();g.cl ipRe ct(x, y, width, height);

}

public void rest oreSafeCli p(Gra phic s g) {

//if (oldClip Bounds==nu ll) retur n;g.se tCli p(oldClipB ounds );oldC lipB ounds = nul l;

}

public void pain t(Graphics g) {

g.se tCol or(Setting s.NORMAL_C OLOR );

// draw just in boundssetS afeC lip(g , pos X, posY, width +1, h eight+1);

g.dr awRe ct( posX, posY, width , height );pain tIns ide(g );

rest oreS afeClip(g );}

public void pain tSelected( Graph ics g) {

g.se tCol or(Setting s.SELECTED _COL OR);




public void pain tOutline(G raphi cs g) {

g.se tCol or(Setting s.SELECTED _COL OR);g.dr awRe ct( posX, posY, width , height );

}

public void pain tEdited(Gr aphic s g) {






retu rn getBou nds().cont ains( poin t);}



public void move (int vectorX , int vector Y) {

posX += vector X;posY += vector Y;

}

public void grap hicEdition End () {}

public Coll ectio n gen erateGEPs () {

Arra yLis t res ult= new ArrayList();resu lt.a dd(new Cla ssGEP(this , new Poi nt(po sX+width , posY+heig ht) ) );retu rn result ;

}

public void form Edition () {

// this will chang e cla ss data & appe rance (OK) or not ( Cancel)Clas sEdi tion ce= new ClassEditio n(this , classDa ta);

if (ce.d ataCh anged ()) setSize();

// updat e dat atry {

Reg istry .getD ataTr ansfer(). updat e(thi s );Reg istry .getD ataTr ansfer(). updat e(cla ssDat a );

} catch (Data ObjectNotE xistE xcep tion ex) {EL. repor t(EL. INTER NAL_ERROR , thi s, "Class doesn 't exist with ID " + cla ssID .toSt ring(), ex );

}

Diag ramC anvas.upda teDependen tLin ks(this.ge tID ());Regi stry .getDiagra mActivatio n(). refreshAll DiagramWin dows ();

}

public bool ean hasFor mEdit ion () {

retu rn true;}

}

class ClassG EP extend s Sta ndartGEP {

public Clas sGEP( Graph icObj ect clien tObje ct, P oint posit ion) {

supe r(cl ientObject , pos ition );}

public void move (Point new Position) {

Clas sApp erance nod e= (ClassApper ance)clien tObje ct;

Poin t oldPosi tion= getP osition();int newG epX = (int )oldPositi on.g etX();int newG epY = (int )oldPositi on.g etY();

int curr entX = (int)newPosit ion. getX();int curr entY = (int)newPosit ion. getY();

node .wid th= curren tX- node.posX;if (node .widt h<nod e.MIN IMAL_WIDT H) node.wi dth= node. MINI MAL_W IDTH;newG epX= node .posX + node.width;

node .hei ght= curre ntY- node.posY;if (node .heig ht<no de.MI NIMAL_HEI GHT ) node. heigh t= node.M INIMA L_HEIGHT ;newG epY= node .posY + node.height ;

upda teOw nPosition( new Point(newG epX, newGe pY));}

}

package pwuml.elements.links.inheritance;

import javax.swing.*;import java.awt.*;

import pwuml.*;import pwuml.error.*;import pwuml.data.diagram.*;import pwuml.diagrammanagement.*;import pwuml.data.base.*;import pwuml.data.datastorage.*;import pwuml.elements.nodes.classes.*;import pwuml.elements.nodes.interfaces.*;

public class InheritanceSelection extends ToolSelection {

public InheritanceSelection(ToolBar toolBar) {

super(toolBar);}

public String getIconFileName() { return "inheritance.gif"; }

public String getToolTip() {

return "Inheritance";}

public GraphicLink createLink(DiagramID diagramID, GraphicNodeID sourceID, GraphicNodeID destinationID)

throws ImproperLinkException {

// checking nodes

// selfreferencing not allowedif (sourceID.equals(destinationID)) throw new

ImproperLinkException("Selfreferencing not allowed.");

DataTransfer dt = Registry.getDataTransfer();

DataObject sourceNode = null;DataObject destinationNode = null;

try {sourceNode = dt.get(sourceID);destinationNode = dt.get(destinationID);

} catch (DataObjectNotExistException ex) {EL.report(EL.INTERNAL_ERROR, this, "Node can't be found

with ID " +sourceID.toString() + " or " + destinationID.toString() );

return null;}

// classes or interfaces must be selectedboolean testOk= false;

if ( sourceNode instanceof ClassApperance && destinationNode instanceof ClassApperance )

testOk= true;

if ( sourceNode instanceof InterfaceApperance && destinationNode instanceof InterfaceApperance )

testOk= true;

if (!testOk) throw new ImproperLinkException("Improperinheritance.");

Inheritance newLink= new Inheritance( Registry.getDataTransfer().getNewID(), diagramID,

sourceID,destinationID );

return (GraphicLink)newLink;}

public GraphicNode createNode(DiagramID diagramID, Point p) {

return null;}

public boolean isNode() {

return false;}

}


import java.awt.*;import java.awt.event.*;import java.util.*;import javax.swing.*;import javax.swing.event.*;





window.*/



}





}


}


}


}





}


}


}


}


}





}



}


import java.awt.*;import java.awt.event.*;import java.util.*;import javax.swing.*;import javax.swing.event.*;





window.*/



}





}


}


}


}





}


}


}


}


}





}



}

package pwuml.ele ments. nodes .classes ;

import ja va.awt.*;import ja va.awt .geom.*;import ja va.uti l. *;

import pwuml. *;import pwuml. error. *;import pwuml. data.b ase.* ;import pwuml. data.d atastorage. *;import pwuml. data.d iagram.DiagramI D;import pwuml. graphicbase .*;import pwuml. diagramma nagement .*;import pwuml. diagramma nagement.gr aphicedition .*;

/***** @author david*/public class ClassApperance exte nds GraphicNode {

/*** ID of Class object which contains class data.*/ClassDataID classID;

protectedint posX ;protectedint posY ;

protectedint width;protectedint height;

transient ClassData classData;MethodRenderer metho dRend erer;

protectedboolean fullName= false;protectedboolean showAttributes= true;protectedboolean showMethods= true;

static int MINIMAL_WIDTH; // we will ev aluate it after "em pty" class is createdstatic int MINIMAL_HEIG HT;

final static int FIE LD_ALIGN_LEFT = 0;final static int FIE LD_ALIGN_CENTER = 1;final static int LE FT_MARGIN = 10;final static int VERTICAL_SPACE = 4;int yPointer;

boolean sizeFound = false;

public ClassApperance(ClassApperanceID newObjectID, DiagramI D diagramID , ClassDataI D classID) {

super((GraphicNodeID )newO bjectID, diagramID);this.classID= classID;addMaster(classID);

meth odRe nderer= new MethodRen derer ();loadData();setSize();

MINIMAL_WIDT H= width;MINIMAL_HEIGH T= he ight;

}

void loadData() {

try {DataTransfer dt= Re gistry.getD ataTransfer( );classData= ( ClassDa ta) dt.get(cl assID);

} catch(DataObjectNotExistException ex ) {EL .report(EL.I NTER NAL_ERROR , this, "Class doesn't exist with ID " + classID.toString( ), ex) ;

}}


return classID;}

protectedvoid reloadAdditiona lData( ) {

loadData() ;}


yPointer= posY;}

void a ddField(Gra phicsg, String text, Font font, intalign) {

g.set Font(font);FontMetricsmetrics = g.getF ontMetrics() ;int textWidth= metrics.stringWidth(text);int textHei ght= metri cs. getHeight();

int textX;int textY= yPointer + VERTIC AL_SPACE + metrics.getAscent();

if (align== FIEL D_ALIGN_LE FT ) textX= posX + LEFT _MARGIN;else textX= (int) ( posX + (width- textWidth)/2 );

g.drawString(text, textX, textY);yPointer+ = textHeight + VERTICAL_SPACE;

}

void a ddFieldSepa rator(Graphics g) {

yPointer+ = VERTICAL_SPACE;g.drawLine( posX, yPointer, posX+width, yPointer);

}

/*** Eval uates width and height so all fields a re visible.*/void setSize() {

height= 0;width= 0;

FontMetricsdataMetrics = Re gistry.getD ataFontMetrics();FontMetricstitle Metrics = Re gistry.getTitleFont Metrics();int textWidth;int textHei ght;

// titletextWidth = titleMetrics.stringWidth(classData. name );textHeight = titleMetrics.get Height ();height += VERTICAL_SPACE + textHeight;if (width<textWidth) width= textWidth;

// title- attributes separatorheight+= VERTI CAL_SPACE;



for (int i=0; i<classDa ta.attributes.size( );i++ ) {

AttributeData att= ( AttributeData) classData .attributes. get(i);StringattributeNam e = att.toString();

textWidth= dataMe trics.stringWidth(attributeNam e ) + L EFT_ MARGI N;if (width< textWidth) width= textWidth;height+ = VERTICAL_SPACE + textHeight;

}

// attributes- methods separatorheight+= VERTI CAL_SPACE;

// m ethods/*g.set Font(Settings.dat aFont );metrics = g. getF ontMetrics() ;textHeight = me trics.getHeight();*/

if (showMethods)for (int i= 0;i<classData.met hods. si ze();i ++) {

MethodDatam et= ( MethodData) classData. metho ds.get (i);String me thodName = meth odRenderer .rend erMethod(m et);textWidth= dataMetrics.stringWidth(m ethodName) + LE FT_MARGIN;if ( width<text Width) width= textWidth;height+ = VERT ICAL_SPACE + textHeight;

}

height+= VERTI CAL_SPACE;width+= 1 0;

sizeFound= true;}

void paintIn side (Graphics g) {

rese tFie ldAddition ();addF ield (g, classD ata.n ame , Settings. titleFont , FIEL D_ALIGN_C ENTER);addF ield Separator( g);

if (show Attri butes )for ( int i=0;i< class Data. attribute s.siz e();i ++) {

Attribu teData att = (Attrib uteDa ta) classD ata.attri butes .get( i);String attri buteN ame = att.toStr ing();

addFiel d(g, attri buteName, Sett ings. dataFont , FIELD_ALI GN_LE FT);}

addF ield Separator( g);if (show Metho ds)

for ( int i=0;i< class Data. methods.s ize() ;i++) {

MethodD ata met= ( MethodDat a) classDa ta.methods .get (i );String metho dName = methodR ender er.renderM ethod(met );

addFiel d(g, metho dName , Setting s.dataFont , FIE LD_ALIGN_ LEFT);}

}

Rectang le oldCli pBounds = null;

public void setS afeCl ip(Gr aphic s g, int x, int y, int width , int heig ht) {

oldC lipB ounds = g.g etClipBoun ds();g.cl ipRe ct(x, y, width, height);

}

public void rest oreSa feCli p(Gra phics g) {

//if (oldClip Bounds==nu ll) retur n;g.se tCli p(oldClipB ounds );oldC lipB ounds = nul l;

}

public void pain t(Gra phics g) {

g.se tCol or(Setting s.NORMAL_C OLOR );




public void pain tSele cted( Graph ics g) {





public void pain tOutl ine(G raphi cs g) {

g.se tCol or(Setting s.SELECTED _COL OR);g.dr awRe ct( posX, posY, width , height );

}

public void pain tEdit ed(Gr aphic s g) {






retu rn getBou nds().cont ains( poin t);}



public void move (int vecto rX, int vector Y) {

posX += vector X;posY += vector Y;

}

public void grap hicEd ition End () {}

public Coll ectio n gen erateGEPs () {

Arra yLis t res ult= new ArrayList();resu lt.a dd(new Cla ssGEP(this , new Poi nt(po sX+width , posY+heig ht) ) );retu rn result ;

}

public void form Editi on() {

// this will chang e cla ss data & appe rance (OK) or not ( Cancel)Clas sEdi tion ce= new ClassEditio n(this , classDa ta);

if (ce.d ataCh anged ()) setSize();

// updat e dat atry {

Registry .getDataTr ansfe r(). updat e(this );Registry .getDataTr ansfe r(). updat e(classDat a );

} catch (Data Objec tNotE xistE xception ex) {EL.repor t(EL.INTER NAL_E RROR , thi s, "Class doesn 't exist with ID " + cla ssID .toSt ring(), ex );

}

Diag ramC anvas.upda teDependen tLin ks(this.ge tID ());Regi stry .getDiagra mActivatio n(). refreshAll DiagramWin dows ();

}

public bool ean hasFor mEdit ion () {

retu rn true;}

}

class ClassG EP extend s Sta ndartGEP {

public Clas sGEP( Graph icObj ect clien tObje ct, P oint posit ion) {

supe r(cl ientObject , pos ition );}

public void move (Poin t new Position) {

Clas sApp erance nod e= (ClassApper ance)clien tObje ct;

Poin t oldPosi tion= getP osition();int newG epX = (int )oldPositi on.g etX();int newG epY = (int )oldPositi on.g etY();

int curr entX = (int)newPosit ion. getX();int curr entY = (int)newPosit ion. getY();

node .wid th= curren tX- node.posX;if (node .widt h<nod e.MIN IMAL_WIDT H) node.wi dth= node. MINIMAL_W IDTH;newG epX= node .posX + node.width;

node .hei ght= curre ntY- node.posY;if (node .heig ht<no de.MI NIMAL_HEI GHT ) node. heigh t= node.MINIMA L_HEI GHT;newG epY= node .posY + node.height ;

upda teOw nPosition( new Point(newG epX, newGe pY));}

}

package pwuml.elements.links.inheritance;

import javax.swing.*;import java.awt.*;

import pwuml.*;import pwuml.error.*;import pwuml.data.diagram.*;import pwuml.diagrammanagement.*;import pwuml.data.base.*;import pwuml.data.datastorage.*;import pwuml.elements.nodes.classes.*;import pwuml.elements.nodes.interfaces.*;

public class InheritanceSelection extends ToolSelection {

public InheritanceSelection(ToolBar toolBar) {

super(toolBar);}

public String getIconFileName() { return "inheritance.gif"; }

public String getToolTip() {

return "Inheritance";}

public GraphicLink createLink(DiagramID diagramID, GraphicNodeID sourceID, GraphicNodeID destinationID)

throws ImproperLinkException {

// checking nodes

// selfreferencing not allowedif (sourceID.equals(destinationID)) throw new

ImproperLinkException("Selfreferencing not allowed.");

DataTransfer dt = Registry.getDataTransfer();

DataObject sourceNode = null;DataObject destinationNode = null;

try {sourceNode = dt.get(sourceID);destinationNode = dt.get(destinationID);

} catch (DataObjectNotExistException ex) {EL.report(EL.INTERNAL_ERROR, this, "Node can't be found

with ID " +sourceID.toString() + " or " + destinationID.toString() );

return null;}

// classes or interfaces must be selectedboolean testOk= false;

if ( sourceNode instanceof ClassApperance && destinationNode instanceof ClassApperance )

testOk= true;

if ( sourceNode instanceof InterfaceApperance && destinationNode instanceof InterfaceApperance )

testOk= true;

if (!testOk) throw new ImproperLinkException("Improperinheritance.");

Inheritance newLink= new Inheritance( Registry.getDataTransfer().getNewID(), diagramID,

sourceID,destinationID );

return (GraphicLink)newLink;}

public GraphicNode createNode(DiagramID diagramID, Point p) {

return null;}

public boolean isNode() {

return false;}

}


Practice 3 – Manage requirements : requirements modelling vs. documenting


User RequirementsDocument

----------------------------------------------------------------------------------------------------------------------------

User RequirementsModel

cd Diagram klas

Sa mochód

Właścic ie l

Dow ód Rej es tra cyj ny

w spółw łasnoś ć

udokume ntow anie

przynależnoś ć

w łasnoś ć

ud Dia gram przypadków użyc ia

S ystem , , P rzy jazny Wydz iał Ko m uni ka cj i "

Re jes trator

Wła śc ici el

Zar ej es trowanie w ydania dow odu re jes tracyj nego

Zgłoszenie chęci rej estrac j i sam ochodu

Zgłosze nie zapotrzebow ania na dow ód re jestrac yjny

Spraw dzenie stanu rej estrac j i

Software RequirementsDocument

----------------------------------------------------------------------------------------------------------------------------

Software RequirementsModel










[nie ][t ak]










[nie ][t ak]










[nie ][t ak]

cd Diagram klas

Samoch ód

Właśc iciel



udoku mentowa nie

przynależ noś ć

własn ość

cd Diagra m klas

Samoch ód

Właś ciciel

Dowód Rej es tracyjny

ws półwł asno ść

udok umentowanie

przynależ ność

wł asno ść

cd Diagram klas

Samoch ód

Właśc iciel



udoku mentowa nie

przynależ noś ć

własn ość

Design products

Generallevel

Detailedlevel

Generate!


What is a requirement?

Requirement is a property of the final product (here: a software system) that it needs to possess in order to fulfil the client’s needs. This property can determine the way in which the system should function or specify a quality feature of the system.

Requirement

Software System

!

?!

Requirements control the software development process

Requirements are there to verify that the system was built to its purpose


How do we classify requirements?

By level of detail – one level is not enough (we need to manage complexity) User Requirements – general requirements defining the scope of

the system: “how much will the system do?”, “how much will the system cost us?”, “what business benefits will the system offer?”

Software Requirements – detailed requirements defining specific characteristics of the system: “how will the system ‘talk’ with the user?”, “what data will the system handle?”

By their meaning for the system Functional requirements – what the system will do? Non-functional requirements – what quality will the system have? Vocabulary requirements – what data will the system handle? Environmental constraints – what limits are there in the client’s

environment (technical or business)?


How to manage requirements?

Divide your requirements document or model into “chunks”. Each chunk is a single requirement.

Individual requirements are related one to another and related to design products.

Requirements are given attributes (numbers, priorities, etc.).

How to divide the requirements into chunks? This course is to give answer to this!



ad Dia gram czynno ści

Rozp oczęci e reje stracji

Zakończen ie rej estracj i

Rejes trator podaje nazw isko do re jestra cji.

System w yszuk uje wł aścic iela o pod anym nazw isku.

czy znale zniono ?

System rejest ruje s amoch ód znalez ioneg o właś ciciel a.

System p owiad amia r ejestr atora o zarejes trowa niu sa moch odu.

System powia damia rejes trator a o niez nalez ieniu w łaści ciela.

[nie]

[tak]






czy znale zniono ?




[nie]

[tak]

1 2

3

12

34






czy znale zniono ?




[nie]

[tak]


stacja_pc

«jar »Rej es trac ja.ja r

serwer_aplikacyjny

serwer_bazy_danych

«SQL db»DBA ccess.db

«jar»W ydzia l.jar

«ja r»Sta tys tyki.jar



DaneOsob oweIOsoby

DaneR ejestr acji



cd Di agram klas

Sam ochód

Właściciel

Dowód Rej est racyj ny

w spół własność

udoku ment owanie

przynależno ść

w łasność

cd Di agram klas

Sam ochód

Właściciel

Dowód Rej est racyj ny

w spół własność

udoku ment owanie

przynależno ść

w łasność


How do requirements control the software development process?

Individual requirements (mainly – functional) can control the technical process.

This way, the system is developed in accordance with the user’s needs.

SO Da

Pracownik dydaktyczny

Student

Przej rzenie planu zajęć z

zarządzaniem ocenami

Dodanie sprawdzianu

Modyfikacja sprawdzianu

Wprowadzenie ocen cząstkowych

Zatwierdzenie ocen końcowych

Wprowadzenie kryteriów

obliczania oceny końcowej

Sprawdzenie ocen z zajęć

Uprawniony pracownik dydaktyczny

Przejrzenie planu zajęć

«ex te n d»«ex te nd »

SODa

Obejrzenie listy studentów

Potwierdzenie złożenia indeksu

Potwierdzenie skreślenia studenta

Przejrzenie historii osiągnięć

studenta

Dokonanie rejestracji studenta po

terminie

Obejrzenie listy studentów przez

Dziekana

Potwierdzenie wydania indeksu

Dokonanie zmiany rejestracj i

studenta

Przydzielenie studentów do grup

Dziekan

Pracownik dziekanatu Obej rzenie listy

studentów przez pracownika dziekanatu

«extend»

«extend»

«i nclude»«extend»

«extend»

«extend»«extend»

«include»«extend»

36

5 2

1 712 10

811

913

4 1817

151614

Jakaś zmiana wymagani.Bardzo istotna zmiana wymagania




UżytkownikZamawiający

1 2 3

Analityk wymagańAnalysts


Summary: methodologies – what’s the problem?

People don’t use methodologies

Even if people try to use methodologies, they don’t use them correctly. Formal methodologies

become “too heavy” – documents overwhelm the process (see: analysis paralysis)

Agile methodologies become too light – “code hacking” substitutes systematic techniques and adequate documenting

?


Summary: methodologies – what’s the answer?

Modelling! Instead of writing heavy specifications – draw simple to understand

diagrams

Iterations! Instead of doing everything in one “big bang” (oh, what a mess!) –

divide the project into several smaller “bangs”

Requirements drive the process! Instead of writing the system based on vague vision – define very

precise requirements “chunks” and assure that they are realized “one by one”


Software RequirementsModel

Summary: how will WE do it?

Assigned subject

User RequirementsDocument (ver. 1)

----------------------------------------------------------------------------------------------------------------------------


Software RequirementsDocument (ver. 1, 2, 3)

----------------------------------------------------------------------------------------------------------------------------










[nie ][t ak]










[nie ][t ak]










[nie ][t ak]

cd Diagra m klas

Samoch ód

Właś ciciel



udok umentowanie

przynależ ność

wł asno ść

cd Diagram klas

Samoch ód

Właśc iciel



udoku mentowa nie

przynależ noś ć

własn ość

cd Diagra m klas

Samoch ód

Właś ciciel



udok umentowanie

przynależ ność

wł asno ść

Design products

1

1

2

2 3

3

4 56

7

10

118

91