1 / 7

Land

Come to grips with the information! Information Models in Software Projects peter.tallungs@objectware.se Dataföreningens UML-nätverk 6 september 2007. Kommun. Region. Län. Land. Handläggare. Utl person- nr land. Är folk bokförd i. Medborgar- skap. Adress. Kontakt. Utländsk adress.

mariel
Download Presentation

Land

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Come to grips with the information! Information Models in Software Projectspeter.tallungs@objectware.se Dataföreningens UML-nätverk 6 september 2007 Kommun Region Län Land Handläggare Utl person-nr land Är folk bokförd i Medborgar-skap Adress Kontakt Utländsk adress Provbana Person Svensk adress Förordnande Notering Blankett Förordnande

  2. Models in Unified Process BusinessUse Case Model - Workers - Entities - Events - Rules - Systems BusinessAnalysis Model Use Case Model Analysis Model Design Model Data Model

  3. What knowledge do we have to capture? Goals expresses what you want to do with governs motivates Processes controls works with Rules sets boundaries for Resources Business Software Requirements Effects Function Rules Information

  4. Requirements Discipline lacks Information View. Business Modelling Discipline The Business Entities are skipping over the Requirement Discipline. The Requirement Discipline lacks an information view. It has only a functional view Requirement Discipline Analysis and Design Discipline

  5. The problem with Unified Process The information view gets no focus To deep embedded in the Business Modelling Discipline. Missing altogether in the requirements discipline. Made worse by: Business Modelling is seldom made according to UP, more often process modelling alone.

  6. What is the effect? Different projects tackles this deficiency in different ways: Strategy 1: The project is faithful to UPSince UP says Use Cases is all there is, you stick to Use Cases. Result: Knowledge and solution will be instable. There will be late surprises. A project heavy in information will not deliver at all. Strategy 2: ”Data descriptions” are squeezed in to the Use Case descriptions. Result: The Use Case descriptions gets heavy and hard to change. Same knowledge gets recorded in many places. The project will not respond easily to changed requirements and new insights. Strategy 3: Separate ”Data descriptions” are made. Result: This is better, but the information analysis gets to small attention. You do not really apprehend what a good information analysis look like.

  7. What to do then? Set up an information model in the Business Modelling.Let the information model hang on right through the project. Dress it up step by step with information requirements and solutions. Make the model rich.Graphs and structured text integrated in the same document. Let the information model carry the business rules. Result: The communication gets more efficient. You are establishing (and further develops) a rich common language between all stakeholders. The Use Cases can be kept light and agile.The Use Case Overview will do in most cases. There is always a natural place to record a piece of knowledge or question at issue. No need for lose pieces of requirements and issues.. The project will be agile (where it should be agile)and stringent (where structure and details are needed).

More Related