100% tevredenheidsgarantie Direct beschikbaar na je betaling Lees online óf als PDF Geen vaste maandelijkse kosten
logo-home
Eerder door jou gezocht
Eerder door jou gezocht
logo
UML Summary €3,99
In winkelwagen
Snel navigeren naar
Voorbeeld
  2.  
  3. Katholieke Universiteit Leuven (KU Leuven)
  4.  
  5. Master Of Business Information Management
  6.  
  7. Seystems Developments and Economics (HMH7)

Samenvatting

UML Summary
 0 keer verkocht

Business Information Management: Second part of the Systems Development and Economics subject: UML. This document contains all the slides, notes from 2 students and extra information collected on Internet. I had a 16 out 20 for this subject.

Voorbeeld 4 van de 42  pagina's

Document informatie

  • 19 februari 2019
  • 42
  • 2018/2019
  • Samenvatting

Onderwerpen

  • uml
  • business information management
  • systems development and economics
  • master in handelswetenschappen

Geschreven voor

Alle documenten voor dit vak (1)

Verkoper

avatar-seller
shafaqsara

Ontvangen beoordelingen

Voorbeeld van de inhoud

UML
1 Essentials of Visual Modeling with UML 2.5
1.1 Principles of Visual Modeling
Objectives
- Describe the importance of visual modeling and the role of Model Driven Architecture.
- Define the four principles of visual modeling.
- Explain what the Unified Modeling Language (UML) represents. • Define the type of process
that best relates to the UML.
Note:
The Unified Modeling Language (UML) is a general-purpose, developmental, modeling language in
the field of software engineering, that is intended to provide a standard way to visualize the design
of a system. The creation of UML was originally motivated by the desire to standardize the disparate
notational systems and approaches to software design. It was developed by Grady Booch, Ivar
Jacobson and James Rumbaugh at Rational Software in 1994–1995, with further development led by
them through 1996.
RUP: a methodology uses explicitly UML which is open, but RUP is commercial. The Rational Unified
Process (RUP) is an iterative software development process framework created by the Rational
Software Corporation, a division of IBM. RUP is not a single concrete prescriptive process, but rather
an adaptable process framework, intended to be tailored by the development organizations and
software project teams that will select the elements of the process that are appropriate for their
needs. RUP is a specific implementation of the Unified Process.
- A collection of models, which have been designed more or less together which means that you
have traceability between models. These will be the models we will use in the Accenture case.
- Different stakeholders need to communicate the same language→relay on and share
- You can use UML fully independent from RUP
- The common language is UML, it is important that they all speak the same language.
- RUP will be defined later on. The goal is to give a method in order, a plan driven method that
uses UML explicitly.
- UML is an open standard.
- RUP was a commercialized project.
- Structure that is given by UML in order to understand the process of RUP is very interesting.
RUP is one of the best methods for software development ever -Yves
- RUP gives life to UML
- UML is mostly used outside of the RUP \When you use RUP, implicitly you use UML.

Who should model in Business system?




Software Project Management Process

,- Key structure of RUP - if you look at the disciplines without the phases, you have the waterfall
cycle. Config - environment are support disciplines. The Phases - at the end of each phase you
have a milestone. Each phase is made of one or more iterations. At the end of an iteration you
need to produce something useable or testable. At the end of each phase you have a milestone,
95% of your use case diagram should be stable, 95% of erd, 95% of code stable, and then it is
finished.
- As is=business modeling & To be= Requirements
- Each phase consists of one or more iterations →same as Agile method →number of iterations
depends on project
- More effort: More presentation of your business and more implementation at the end
- At tran #1, you have a product that works
-
Software Project Management Process:




Major Milestones: Business Decision Points




Project Management Organized into Disciplines
OO Analysis vs. OO Design


What Is a Model?

,Project Management Organized into Disciplines
Disciplines: A collection of activities that are all related to a major “area of concern.”
- The disciplines are:
o Business Modeling - present situation as is
o Requirements - present the situation to be
o Analysis & Design - how can we support the new sw solution
o Implementation - fully implemented
o Test
o Deployment
o Configuration & Change Management
o Project Management - the activities of the pm, not an engineering activity because it is not
the purpose to build a software product, rather to manage the progress of the sw product.
o Environment

OO Analysis vs. OO Design
- Analysis refers to understanding the problem.
- Design refers to coming up with the solution.
- Don’t confuse with broader use of word “design”
- Text replaces “design” with “resolution”

What is a model?
- A model is a simplification of reality
Note:
- Model is a representation of organizational reality in our perspective of what the user is
expecting from the system and how the system needs to perform in order to successfully meet
the user’s requirements.
- A model is an abstraction of reality →put reality on a sheet of paper

Why Model?
- Modeling achieves four aims:
o Helps you to visualize a system as you want it to be.
o Permits you to specify the structure or behavior of a system.
o Gives you a template that guides you in constructing a system.
o Documents the decisions you have made.
- You build models of complex systems because you cannot comprehend such a system in its
entirety.
- You build models to better understand the system you are developing.

Note:
- A model is an abstraction of reality íput reality on a sheet of paper
- You have a problem to solve→As is situation→ need to define the To be situation first
- Make choices and document them
The Importance of Modeling
Less important More important

, Model Driven Architecture (MDA)
- An approach to using models in software development
o Separate the specification of the operation of a system from the details of the way that
system uses the capabilities of its platform.
▪ specifying a system independently of the platform that supports it
▪ specifying platforms
▪ choosing a particular platform for the system
▪ transforming the system specification into one for a particular platform

Note:
- Once you have built your class diagram→can program in certain programming language
- The programming language will have an impact on the project of how the software needs to be
built. Define language independently of the technology, and once you have your models and
case tools you can generate specific situations, use genetic code, and linking platforms. Once
you've built your class diagram you can use programming languages code straight out of your
class diagram.
- We will stay at the platform dependent way.

What is UML?
- The UML is a language for
o Visualizing
o Specifying
o Constructing
o Documenting
- the artifacts of a software- intensive system→UML is best known, but there are more ML

The UML Is a Language for Visualizing
- Communicating conceptual models to others is prone to error unless everyone involved speaks
the same language.
- There are things about a software system you can’t understand unless you build models.
- An explicit model facilitates communication.

Note:
- Interesting because everyone speaks the same language→all stakeholders know UML
- Different views from different stakeholders on a project→goal is to facilitate communication
- The stakeholders all know it
- Model is general, diagram is an instance.
- If you draw a use case diagram for a specific case, it’s a diagram for an instance. Use-case and
activity diagrams help us present the situation as is and the situation to be in terms of high level
structures, non-technical workflows. Main design diagrams which help to shape the solution,
document how the system should behave (class, sequence and communication (are very
similar)) Component/composite forget about.
- Behavioral diagrams - give you dynamic/ what happens before/after
- Structural - static, structure

Dit zijn jouw voordelen als je samenvattingen koopt bij Stuvia:

Bewezen kwaliteit door reviews

Bewezen kwaliteit door reviews

Studenten hebben al meer dan 850.000 samenvattingen beoordeeld. Zo weet jij zeker dat je de beste keuze maakt!

In een paar klikken geregeld

In een paar klikken geregeld

Geen gedoe — betaal gewoon eenmalig met iDeal, Bancontact of creditcard en je bent klaar. Geen abonnement nodig.

Focus op de essentie

Focus op de essentie

Studenten maken samenvattingen voor studenten. Dat betekent: actuele inhoud waar jij écht wat aan hebt. Geen overbodige details!

Veelgestelde vragen

Wat krijg ik als ik dit document koop?

Je krijgt een PDF, die direct beschikbaar is na je aankoop. Het gekochte document is altijd, overal en oneindig toegankelijk via je profiel.

Tevredenheidsgarantie: hoe werkt dat?

Onze tevredenheidsgarantie zorgt ervoor dat je altijd een studiedocument vindt dat goed bij je past. Je vult een formulier in en onze klantenservice regelt de rest.

Van wie koop ik deze samenvatting?

Stuvia is een marktplaats, je koop dit document dus niet van ons, maar van verkoper shafaqsara. Stuvia faciliteert de betaling aan de verkoper.

Zit ik meteen vast aan een abonnement?

Nee, je koopt alleen deze samenvatting voor €3,99. Je zit daarna nergens aan vast.

Is Stuvia te vertrouwen?

4,6 sterren op Google & Trustpilot (+1000 reviews)

Afgelopen 30 dagen zijn er 69411 samenvattingen verkocht

Opgericht in 2010, al 15 jaar dé plek om samenvattingen te kopen

Start met verkopen
€3,99
  • (0)
In winkelwagen
Toegevoegd