100% satisfaction guarantee Immediately available after payment Both online and in PDF No strings attached
logo-home
Previously searched by you
Previously searched by you
logo
Summary 2-page Overview INFOMSO $3.23
Add to cart
Quickly navigate to
Preview
  2.  
  3. Universiteit Utrecht (UU)
  4.  
  5. Modelleren En Systeemontwikkeling (INFOMSO)

Summary

Summary 2-page Overview INFOMSO
 2 purchases
  • Course
  • Modelleren En Systeemontwikkeling (INFOMSO)
  • Institution
  • Universiteit Utrecht (UU)

2-page overview of all the subjects discussed in the Modelleren en Systeemonwikkeling course, very concisely summarized. One page for the midterm, one for the final. Summary of the summary.

Preview 1 out of 2  pages

Document information

  • November 12, 2021
  • 2
  • 2021/2022
  • Summary

Subjects

  • waterfall method
  • spiral model
  • agile
  • unified process
  • requirements
  • class diagram
  • analysis
  • design
  • facade
  • adapter
  • strategy
  • bridge
  • abstract factory
  • decorator
  • mvc
  • observer
  • template method
  • factory
  • up
  • furps

Written for

  • Universiteit Utrecht (UU)
  • Informatica
  • Modelleren En Systeemontwikkeling (INFOMSO)
All documents for this subject (4)

Seller

avatar-seller
Suniht

Reviews received

Content preview

MSO‌‌Midterm‌ ‌
‌

Waterfall‌‌method‌ ‌ 4. Negotiation‌‌(with‌‌client)‌ ‌ - Parameter‌‌visibility‌‌(method‌‌of‌‌A)‌ ‌
- 5‌‌consecutive‌‌phases:‌ ‌ - 6‌‌demands‌‌for‌‌good‌‌requirements‌ ‌ - Local‌‌visibility‌‌(B‌‌as‌‌local‌‌object)‌ ‌
1. Requirements‌‌analysis‌ ‌ - Correctness‌‌(capture‌‌client‌‌view)‌ ‌ - Global‌‌visibility‌ ‌
2. Design‌ ‌ - Consistency‌‌(no‌‌contradictions)‌ ‌
Facade‌ ‌
3. Coding‌‌and‌‌debugging‌ ‌ - Completeness‌‌(all‌‌scenarios)‌ ‌
- Provide‌‌a‌‌unified‌‌interface‌‌(API)‌ ‌to‌‌
4. Testing‌‌and‌‌verification‌ ‌ - Clarity‌‌(unambiguous)‌ ‌
a‌‌set‌‌of‌‌interfaces‌‌in‌‌a‌‌sub-system‌ ‌
5. Maintenance‌ ‌ - Realism‌ ‌
- Encapsulates‌‌original‌‌system,‌‌thus‌‌
- Unable‌‌to‌‌deal‌‌with‌‌change‌ ‌ - Verifiability‌‌(automatic‌‌testing)‌ ‌
easy‌‌to‌‌swap‌‌out‌‌or‌‌change‌‌(without‌‌
- Users‌‌involved‌‌late‌‌in‌‌project‌ ‌ - SMART‌‌requirements‌ ‌
client‌‌noticing)‌ ‌
Spiral‌‌model‌ ‌ Class‌‌diagram‌ ‌
Adapter‌ ‌
- Iterative‌‌waterfall,‌‌focus‌‌on‌‌risk‌ - Inheritance:‌‌A⇽B,‌‌A‌‌superclass‌‌of‌‌B‌ ‌
- Match‌‌an‌‌existing‌‌class‌‌beyond‌‌
- Aggregation:‌‌A⬦‌ー‌B,‌‌A‌‌has‌‌attrib‌‌B‌ ‌
Agile‌ ‌ your‌‌control‌‌to‌‌a‌‌particular‌‌interface‌ ‌
- Association:‌‌A→B,‌‌more‌‌general‌‌↑‌ ‌
- Agile‌‌vs‌‌UP:‌ ‌ - Contain‌‌existing‌‌class‌‌in‌‌your‌‌own‌‌
- Composition:‌‌A⬥‌ー‌B,‌‌B‌‌has‌‌no‌‌right‌‌
- Interactions‌‌vs‌‌processes‌ ‌ Adapter‌‌class‌‌with‌‌right‌‌interface‌‌
to‌‌exist‌‌on‌‌its‌‌own‌ ‌
- Prototypes‌‌vs‌‌documentation‌ ‌ and‌‌that‌‌calls‌‌existing‌‌methods‌ ‌
- Dependency:‌‌A⇢B,‌‌A‌‌uses‌‌B,‌‌
- Collaboration‌‌vs‌‌negotiation‌ ‌
change‌‌to‌‌A‌‌affects‌‌B‌ ‌ Strategy‌ ‌
- Embrace‌‌change‌‌vs‌‌clear‌‌plan‌ ‌
- Find‌‌what‌‌varies‌‌and‌‌encapsulate‌‌it‌‌
- No‌‌redundancy‌ ‌ Analysis‌ ‌
in‌‌abstract‌‌class,‌‌with‌‌subclasses‌‌
- Readability‌‌(e.g.‌‌good‌‌naming)‌ ‌ - Make‌‌domain‌‌model‌‌from‌‌reqrmnts‌ ‌
for‌‌variation‌ ‌
- Testability‌ ‌ - Capture‌‌user’s‌‌point‌‌of‌‌view‌ ‌
- Contain‌‌abstract‌‌in‌‌original‌‌class‌ ‌
- Model‌‌real‌‌world‌‌classes‌ ‌
Unified‌‌Process‌ ‌ - Separates‌‌selection‌‌of‌‌algorithm‌‌
- Validation‌‌similar‌‌to‌‌requirements‌ ‌
- Iterative‌‌‌(usable‌‌subset‌‌of‌‌system‌‌ from‌‌implementation‌ ‌
‌
after‌‌every‌‌iteration)‌ ‌ - Makes‌‌for‌‌easier‌‌testing‌ ‌
- Phases:‌ ‌ Design‌‌principles‌ ‌
Bridge‌ ‌
1. Inception‌ ‌ - Program‌‌to‌‌interface‌ ‌
- Find‌‌variation,‌‌encapsulate‌‌it‌ ‌ - Decouple‌‌set‌‌of‌‌implementations‌‌
2. Elaboration‌ ‌
- Aggregation‌‌over‌‌inheritance‌ ‌ from‌‌abstractions‌‌(objects‌‌using‌‌
3. Construction‌ ‌
them)‌ ‌
4. Transition‌ ‌
Design‌ ‌ - Two‌‌separate‌‌class‌‌hierarchies,‌‌with‌‌
- Engineering‌‌activities:‌ ‌
- Cohesion:‌‌related‌‌operations‌ ‌ a‌‌bridge‌‌between‌‌them‌ ‌
- Business‌‌modeling‌ ‌
‌‌
- Requirements‌‌engineering‌ ‌ - Coupling:‌‌related‌‌modules‌ ‌
- Analysis‌ ‌ - Data‌‌coupling‌‌(one‌‌method‌‌relies‌‌
- Design‌ ‌ on‌‌data‌‌from‌‌other‌‌method)‌ ‌
- Implementation‌ ‌ - Control‌‌“‌‌(one‌‌instructs‌‌other)‌ ‌
- Testing‌ ‌ - Global‌‌data‌‌“‌‌(global‌‌variable)‌ ‌
- Pathological‌‌coupling‌‌(exact‌‌imp)‌ ‌
Requirements‌ ‌
- 3‌‌perspectives‌‌on‌‌software‌‌dev‌ ‌
- FURPS+‌‌model:‌ ‌ - Conceptual‌‌(domain‌‌concepts)‌ ‌
- Functionality‌‌(features)‌ ‌
- Object‌‌set‌‌of‌‌responsibilities‌ ‌
- Usability‌‌(help/documentation)‌ ‌ - Specification‌‌(interfaces)‌ ‌
- Reliability‌‌(uptime/recovery)‌ ‌
- Object‌‌is‌‌set‌‌of‌‌methods‌ ‌
- Performance‌‌(response‌‌time)‌ ‌ - Implementation‌‌(coding)‌ ‌
- Supportability‌‌(adaptability)‌ ‌ - Object‌‌is‌‌code‌‌and‌‌data‌ ‌
- Sub-factors‌:‌ ‌
- GRASP‌‌(help‌‌assign‌‌responsibility)‌ ‌
- Implementation‌‌(lang‌‌..)‌ ‌ - Information‌‌expert‌ ‌
- Legal‌‌(licensing‌‌..)‌ ‌
- Creator‌‌(create‌‌instances)‌ ‌
- Interface‌‌(other‌‌systems)‌ ‌ - Loose‌‌coupling‌ ‌
- Requirements‌‌engineering:‌ ‌ - Strong‌‌cohesion‌ ‌
1. Elicitation‌‌(identifying)‌ ‌
- Controller‌‌(system‌‌events)‌ ‌
2. Specification‌‌(describing)‌ ‌ - Class‌‌A‌‌can‌‌access‌‌info‌‌in‌‌B‌‌with:‌ ‌
3. Verification/validation‌ ‌
- Attribute‌‌visibility‌‌(B‌‌attrib‌‌of‌‌A)‌ ‌

‌

The benefits of buying summaries with Stuvia:

Guaranteed quality through customer reviews

Guaranteed quality through customer reviews

Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.

Quick and easy check-out

Quick and easy check-out

You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.

Focus on what matters

Focus on what matters

Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!

Frequently asked questions

What do I get when I buy this document?

You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.

Satisfaction guarantee: how does it work?

Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.

Who am I buying these notes from?

Stuvia is a marketplace, so you are not buying this document from us, but from seller Suniht. Stuvia facilitates payment to the seller.

Will I be stuck with a subscription?

No, you only buy these notes for $3.23. You're not tied to anything after your purchase.

Can Stuvia be trusted?

4.6 stars on Google & Trustpilot (+1000 reviews)

68175 documents were sold in the last 30 days

Founded in 2010, the go-to place to buy study notes for 15 years now

Start selling
$3.23  2x  sold
  • (0)
Add to cart
Added