Software Requirements and Design notes
40 notes by 33 users
This GoConqr page gathers notes on Software Requirements and Design, from requirements and validation to architecture and design patterns. It supports university students and professional candidates practising these topics, and teachers looking for material to use. With over 30 notes from more than 20 users, the page is mainly university-level, with some material for professional candidates and school students. Choose a note to get started.
Select topic
- Software Development Methodologies9
- Requirements Engineering34
- Software Requirements Types and Specification30
- User Interface Design and Prototyping17
- Software Design Principles19
- Design Patterns47
- Software Architecture36
- Software Architecture Views and Description15
- Architectural Styles and Patterns55
- Service-Oriented Architecture30
- Microservices Architecture10
- UML Diagrams44
Notes
-
Android Application Architecture The most important thing you should focus on is the separation of concerns in your app. Any code that does not handle a UI or operating system interaction should not be in activity and fragment &...
-
Website Architecture Monolithic vs Microservice Architechture In microservice architecture, each service is self-contained and implements a single business capability. Consider an e-commerce application as a us...
-
3/7 Goal statement: one or two sentences that describe a product and its benefits for the user, focus on who the product will serve, what the product will do and why the product solves the user's need Storyboard: a series...
-
Microservices Spring Cloud provides tools for developers to quickly build some of the common patterns in distributed systems (e.g. configuration management, service discovery, circuit breakers, intelligent routing, micro-proxy, con...
-
MODULE COHESION COHESION It's a measure which defines the level of inter dependability among the elements of a module. The greater the cohesion the better the program design will be. 1.COINCIDENTAL COHESION
-
Untitled ARCHITECTURAL DESIGN It is not the operational software, rather a representation that enables software engineer to 1. analyze effectiveness of the design in meeting the requirements 2. consid...
-
Managing large application architecture How much of this architecture is instantly re-usable? Can single modules exist on their own independently? Could I easily take one of your modules, drop it into a page and it would start working? How much do modules d...
-
Types of Requirements - created from Mind Map What are requirements ? Behaviour or quality a new system is required to have Behaviour requirements are usually called FUNCTIONAL Quality requirements are usually called NON-FUNCTIONAL Something a system must DO Non-...
-
Design patterns There are 3 types: Creational - Singleton, Factory, Abstract Factory, Builder, Prototype Structural - Adapter , composite, Proxy, Flyweight, Facade, Bridge, Decorator Behavioral - Temp;ate Method, Mediator, ...
-
COUPLING Coupling is a measure that defines the level of inter dependability among the modules of a program. It tells at what level the modules interact and communicate with each other. The lower coupling is better for a progr...
-
sre PROPERTIES OF A MODEL: Let’s break down these properties in simpler terms. Each model has three key qualities that make it useful: 1. Mapping of Reality A model represents certain aspects of reality using its own elem...
-
Software Architecture - creado desde un Mapa Mental architectural styles and role in software design THE NOTION OF ARCHITECTURE The inference of system property
-
Software Design Pattern Strategy pattern basic Principals :- 1. Avoid duplication of codes and 2. change in superclass should not break code in sub class neither add any functionality that subclasses cannot perform logically. problem s...
-
To review Cardinality, Multiplicity Notations Relationships and their uses All diagrams once + revision – 1. Class diagram 2. Object diagram (Object model too) 3. Component diagram (Files, libraries, executables, .jar/.java etc...
-
MODULARITY Its the designing of a s/w s/m. The s/m is divided into a set of functional units named modules,that can be composed into a large form of application. A module represents a set of related concerns. It can include a co...
-
TYPES OF REQUIRMENTS - created from Mind Map BUSINESS* USER FUNCTIONAL*
-
FUNCTION ORIENTED DESIGN FUNCTION ORIENTED DESIGN The design activity begins when an SRS document to be developed if available. The design process s/w s/m has two levels. At the first level, the focus is on deciding which modules are needed f...
-
Mockups overview Service API- API to get a list of supported leagues like Seria A, etc.- API to get a list of other kinds of sport disciplines (e.g. Basketball)- API to get matches for given day etc.- API to get live matches - AP...
-
microservice template contract: contracts.v1: swagger.yaml - declaration of the restful api. Easily edited by http://editor.swagger.io/ pom: used to generate interfaces from swagger.yaml file in specific language (in our cas...
-
Chp 4 Requirement Validation - created from Mind Map Requirement Validation Input Output Requirement Document Organization Knowledge Organization Standard List of problem Agreed Action Requirement Review CheckList Processes: Problem Team Member Understandbility Redundan...
-
66. People expect online interactions to follow social rules 66. People expect online interactions to follow social rules There are rules for social interactions that you do and don't even notice. Some rules for social interactions are: eye contact appropriate conversati...
-
8. People Miss Changes In Their Visual Fields Visual Fields Visual Fields refers to the total area where objects can be seen from your peripheral vision, while you are concentrated looking at one thing. Studies have been conducted and concluded that if you are pa...
-
Untitled Singleton class: 1. One Object 2. Return the same object whenever we create a new instance &...
-
TYPES OF S/W DESIGNS TYPES OF DESIGN DATA DESIGN This is the first design activity which results less complex modular and effective program structure. It transforms information domain model into data structures required for implementing t...
-
11. Nine percent of men and one-half percent of women are color-blind Color blindness doesn't mean blind to all colors, it refers to a deficiency in the cones of your eyes causing them to have trouble seeing a difference between colors. Color blindness can come in many form...
-
S/W DESIGN LEVELS ARCHITECTURAL LEVEL It is the highest abstract version of the s/m. It represents s/w as a s/m with all of its components. At this level the designer gets the idea of proposed solution. HIGH LEVEL DESIGN
-
conceptual n technical design The designing of a s/w involves the transformation of ideas into a much more detailed document with the goal of satisfying the requirements. To transform these requirements into a working s/m,the designers must satisf...
-
Arquitecturas reactivas - creado desde un Mapa Mental In a Reactive System, it’s the interaction between the individual parts that makes all the difference, which is the ability to operate individually yet act in concert to achieve their intended result. Problemas Causas
-
Intro to design patterns - Take what varies and "encapsulate" it so it won't affect the rest of your code. The result? Fewer unintended consequences from code changes and more flexibility in your systems! Multiple uses of Interface: Co...
-
Safety and Security Requirements - created from Mind Map What is safety and security requirement? Security Safety Why it is difficult to validate? - Unauthorised access to the system and its data is not allowed Its about the safety of people dealing with the system Many fac...
-
Service ACC-cards - created from Mind Map Provides credit to customers (Companies that works with credit cards) The goverment office needs that each company sends reports Companies require the approval of customers to share data
-
C# Notes on Architectural Patterns
-
1_Swargger Doc basesed config - created from Mind Map validations Routes Try to re design the vaidation from switch case in to OO design
-
Architecture Style Frame - creado desde un Mapa Mental Communication Deployment Domain
-
SQL Layer - created from Mind Map DAO SEVICES Convert ResultSet to Bean MySQL Template DAO Interfaces CONTROLLER Receive Bean from DAO Wrap Bean ActionWrapper Send ActionWrapper to Controller Put URL in ActionWrapper DAO Impl SQL ManagerSend ResultSet...
-
Model, view, whatever Model is our data.e.g. var firstName = 'Tony';View is the thing people see and interact with.e.g. Tony Whatever is whatever binds the model and view so we don't have to update them manually.Names like: Controllers, Vi...
-
lionx_news_provider - created from Mind Map Auth Error gatewayverifica os metodos disponiveis
-
Use of Data Flow Diagrams Data Flow Diagram - depicts the flow of information sequentially Four Components of DFD's - Data Flow - Data Store - Process - Entity
-
Interesting Ruby Talks The value of Value Objects.Value Objects make your code smarter, safer, and more expressive. Learn what Value Objects are, how they help, and some ways to use them in a Rails application.About 23 minutes long New Page
-
What is Software Architecture - Useful structures
More Software Requirements and Design resources
About software requirements and design notes
GoConqr OriginalSoftware requirements and design notes
These user-made notes cover requirements, design patterns and application architecture. The note on types of requirements distinguishes behaviour from quality requirements. Design patterns groups patterns by type, while Microservices looks at tools for distributed systems.
Plan a reading route
Start with the types of requirements note if you want to review the distinction between functional and non-functional requirements. Then read the note on requirement validation to continue along the requirements side of the unit.
For design, Managing large application architecture raises questions about reusable, independent modules. The notes on modularity, coupling and cohesion offer related material on how modules are organised and connected. Use of Data Flow Diagrams and Mockups overview give you other topics to explore.
Change format as you revise
Use the notes to read through a topic, then switch to a mind map on the unit page if you want a visual overview. A quiz can help you check what you remember before returning to a note. Pick a topic and try that route.
Frequently asked questions
Which note should I start with?
Start with the note on types of requirements if you want to review what a system is required to do and the qualities it should have. For a design focus, Managing large application architecture is a place to begin, with questions about reusable and independent modules.
What topics do the notes cover?
The notes cover types of requirements and requirement validation, as well as modularity, coupling and cohesion. You can also find notes on design patterns, microservices, Android application architecture, data flow diagrams and mockups. They give you several routes through the unit, depending on what you want to review.
Are these notes free to use?
Yes. Every resource listed here is free to open and study without an account. The notes were made by GoConqr users, rather than by GoConqr. A free account also lets you save quiz scores and make your own quizzes, mind maps, flashcards and notes.