Help shape GoConqr. What should we add next?

Software Architecture Views and Description

15 resources created by 15 users

This Software Architecture Views and Description page on GoConqr gathers a small set of community-made mind maps and a flashcard deck. They cover architecture views, visual notation and consistency across views. University students can use them to practice recognizing views and describing architectures; teachers can find material on the same topics. The collection is at university level, with several maps to explore alongside the flashcards. Start with a map, then use the flashcards to check your understanding.

Software Architecture Views and Description

Top Software Architecture Views and Description resources

Mind maps

Flashcards

More Software Requirements and Design topics

About Software Architecture Views and Description

GoConqr Original

Start with architecture views

The mind map The 4+1 View Model introduces the logical, process, physical and development views. Its branches include object-oriented decomposition, concurrency and synchronization, software-to-hardware mapping, and static organization. Begin by looking at the view names, then follow their branches to see the aspects each one covers.

A separate map on different views explains that a design or architecture can have multiple views, each looking at different aspects of a system.

Use questions to check the views

After exploring the model, move to the flashcard deck Module 6. Its questions ask about the use case, logical, process, physical and development views. Try answering each question before returning to the map to review the relevant branch.

There are no quizzes on this page, so the flashcards provide the question-led practice in this collection. They also give teachers a way to identify questions to discuss with university students.

Explore descriptions and consistency

The maps titled Description of Software Architectures cover visual notation. One shows square-corner rectangles for hardware components and round-corner rectangles for software components. Another includes examples involving a web client-server pair, robot soccer and a training center management information system.

The maps titled Achieving Consistency Across Views focus on using views to show architecture elements to stakeholders and on the difficulty of keeping views consistent. Compare these maps with the model to connect the view names to the broader question of consistency.

Connect the resources

Within the wider unit in Computing and ICT, these resources bring architecture views together with descriptions of software architectures. The maps offer related ways to look at the topic, while the flashcards provide questions about the views. Choose a map and pair it with the deck for a focused study session.

Frequently asked questions

Which resource should I start with?

Start with The 4+1 View Model if you want an overview of the architecture views. Its branches introduce the logical, process, physical and development views and some of the aspects associated with them. Module 6 is a useful next step because its flashcards ask questions about those views and the use case view.

What do the mind maps cover?

The maps cover architecture views, visual notation and consistency across views. The description maps include questions about components and their relationships, as well as examples of notation. The consistency maps consider how views show architecture elements to stakeholders and the difficulty of keeping those views consistent.

Are these resources free to use?

Yes. Every resource listed on this page is free to open and study without an account. A free account can also save quiz scores and lets you make your own quizzes, mind maps, flashcards and notes. The listed resources were made by GoConqr users.

Feedback

What is it about?

What should we add next?