Study for midterm of SWE 215-Midterm by سعود التميمي https://padlet.com/soa142812222/brdn5gzi557 SWE 215 en-us 2020-02-28 14:27:45 UTC 2020-03-02 11:30:55 UTC hello@padlet.com The Iron Triangle soa142812222 https://padlet.com/soa142812222/brdn5gzi557/wish/452091593 1- Requirement 
2- Cost
3- Schedule ]]> 2020-02-28 16:59:44 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452091593 Successful soa142812222 https://padlet.com/soa142812222/brdn5gzi557/wish/452095354 Satisfied all the Iron Triangle ]]> 2020-02-28 17:04:57 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452095354 Challenging soa142812222 https://padlet.com/soa142812222/brdn5gzi557/wish/452096189 Does not satisfy one or two of the Iron Triangle ]]> 2020-02-28 17:06:15 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452096189 Failed soa142812222 https://padlet.com/soa142812222/brdn5gzi557/wish/452098342 The project get cancelled ]]> 2020-02-28 17:08:57 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452098342 The larger the project, the less valuable the return rate. In many cases larger projects never return value to an organization. soa142812222 https://padlet.com/soa142812222/brdn5gzi557/wish/452101090 2020-02-28 17:12:31 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452101090 The faster the projects go into production soa142812222 https://padlet.com/soa142812222/brdn5gzi557/wish/452101534  the quicker the payback starts to accumulate.]]> 2020-02-28 17:13:03 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452101534 Complexity is often caused by https://padlet.com/soa142812222/brdn5gzi557/wish/452103829
1- size
2-conflicting goals
 3-large budgets ]]> 2020-02-28 17:16:12 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452103829 One of the major causes of both cost and time overruns is https://padlet.com/soa142812222/brdn5gzi557/wish/452107706 restart, Some projects can have several restarts

]]> 2020-02-28 17:21:10 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452107706 The spectrum(sequent) of failures ranges from failures with minor consequences to failure with disastrous effects(bad effects). m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452116186 2020-02-28 17:33:46 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452116186 The reason for many of these failures lay in insufficient requirements engineering: m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452119182 1-Requirements gathering,
2-Requirements documentation, 3-Requirements management. ]]> 2020-02-28 17:38:21 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452119182 *read lecture 1 * m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452119910 from 12 to 14                               
 and 16                                            
and 18  ]]> 2020-02-28 17:39:33 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452119910 The cost of removing defects in requirements increases the later the defects are detected during the development process. m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452121863 2020-02-28 17:42:28 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452121863 Nearly 50% of the failures found in program source code can be traced back to requirements defects. m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452121898 2020-02-28 17:42:32 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452121898 If a requirement defect is detected during programming, the cost to fix the defect is approximately 20 times higher than the effort required to detect and fix the defect during requirements engineering. m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452122219 2020-02-28 17:43:07 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452122219 If the requirements defect is not detected until acceptance testing, the effort required can be up to 100 times greater. m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452122364 2020-02-28 17:43:22 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452122364 RE is always embedded within a specific organizational context(company's products). m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452129127 requirement engineering should be involved in the whole process with any new products from the organisation.]]> 2020-02-28 17:54:02 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452129127 The Term Requirements . m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452143185 (1) Needs and goals of users 

(2) Conditions and properties of the system to be developed 

(3) A documented requirement is called “Requirements Artefact”   
(number 3 means A documented representation of (1) or (2). )]]> 2020-02-28 18:14:34 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452143185 Requirements Abstraction m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452147516 it must define its needs in a sufficiently abstract way that a solution is not pre-defined. The requirements must be written so that several contractors can bid for the contract, offering, perhaps, different ways of meeting the client organization’s needs. ]]> 2020-02-28 18:21:34 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452147516 *read lecture 2* m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452149033 7 and 20]]> 2020-02-28 18:23:56 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452149033 User requirements m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452149791 Statements in natural language plus diagrams of the services(requirements) the system 
provides and its operational constraints

-Written for customers. 

]]> 2020-02-28 18:25:13 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452149791 System requirements m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452151486  A structured document setting out detailed descriptions of the system’s requirements . 



]]> 2020-02-28 18:27:54 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452151486 Why there are Different levels of requirements? m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452153164 because there are different types of readers. ]]> 2020-02-28 18:30:28 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452153164 levels of requirements m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452154327 1- user requirements
2- system requirements]]> 2020-02-28 18:31:54 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452154327 A user requirement may be expanded into several system requirements. m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452155849 2020-02-28 18:34:02 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452155849 Three Requirements Types m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452156535 1. Functional requirements
2. Quality requirements
3. Constraints ]]> 2020-02-28 18:34:59 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452156535 Quality Requirements m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452158345 1- important primarily to users
2-important primarily to developers

examples in the lecture 2  slide 15
very important from 16 to 19]]> 2020-02-28 18:37:39 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452158345 Quality requirements must have a business case, and are not for the sake of the development team. m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452164002 Example: “To improve maintainability, the architecture of the Sales module must be refactored.” ]]> 2020-02-28 18:45:42 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452164002 Types of constraints: m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452168213 1-cultural 
2-legal constraints (from laws and standards)
3-organizational constraints 
4-physical constraints 
5-project constraints ]]> 2020-02-28 18:51:39 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452168213 constraints affect on m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452171979 1 the system itself
2-the development process of the system 

for more detail read slide 24 from lecture 2]]> 2020-02-28 18:56:20 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452171979 Constraints may also lead to the change of requirements or the definition of new requirements m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452176815 2020-02-28 19:02:11 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452176815 Non-functional classifications (types) m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452180527 1-Product requirements 
2-Organizational requirements 
3-External requirements ]]> 2020-02-28 19:07:06 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452180527 Solution space decreases during the development process. m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452184971 for more details see slide 38 from lecture 2]]> 2020-02-28 19:13:16 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452184971 Interactions between requirements and design stage possible m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452185945 2020-02-28 19:14:38 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452185945 The problem definition is typically not independent of the solution definition. m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452192656 A large proportion of requirements are specified with a (preliminary) solution in mind. ]]> 2020-02-28 19:23:42 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452192656 Predictive m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452205351
  •  Software development occurred in an orderly series of sequential stages (Progress flows top to bottom, like a waterfall) 
    • Predictive stages
    1- Requirement 
    2- design
    3- implementation
    4- verification
    5- Deployment


    ]]>     2020-02-28 19:42:43 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452205351     Predictive( Iron Triangle) m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452207952 the requirements are fixed. 
     
    the schedule and budget of the project are estimated.

    (not good)]]>     2020-02-28 19:46:45 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452207952     This “fixed requirements scope” assumption has indeed been found to be a root cause of project failures. m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452210853 (predictive)]]> 2020-02-28 19:51:23 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452210853 “Scope management related to attempting waterfall practices was the single largest contributing factor for failure.” m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452211240 (predictive)]]> 2020-02-28 19:51:56 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452211240 read lecture 3 m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452214024 8
    and 10 (the spiral model)
    and 11 (RAD model)
    and 12(RUP model)]]>     2020-02-28 19:56:29 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452214024     RUP m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452224016 RUP recognized the necessary overlap of the various activities that occurred during the life cycle phases of inception, elaboration, construction, and transition. 

    Requirements elaboration and requirements change are considered to be a continuous process that occurs throughout the life cycle. 


    ]]>     2020-02-28 20:13:42 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452224016     Requirements in Iterative Processes soa142812222 https://padlet.com/soa142812222/brdn5gzi557/wish/452226146 No traditional big, upfront design  but  “discovery based” approach]]> 2020-02-28 20:18:04 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452226146 “discovery based” approach soa142812222 https://padlet.com/soa142812222/brdn5gzi557/wish/452226424 Apply lighter-weight documents and models such as vision documents, use case models, and so on, which are used to initially define what is to be built. ]]> 2020-02-28 20:18:40 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452226424 The iterative process is applied to more quickly discover the “real user requirements” in early iterations, thus substantially reducing the overall risk profile of the project. soa142812222 https://padlet.com/soa142812222/brdn5gzi557/wish/452226834 2020-02-28 20:19:29 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452226834 Examples of adaptive methods: m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452229808 1-Dynamic Systems Development Method (DSDM),     
    2- Feature-Driven Development (FDD),
    3- Adaptive Software Development
    4- Scrum,
     5- Extreme Programming (XP),
    6- Open Unified Process (Open UP),
     7- Agile RUP,
     8- Kanban, 
    9- Lean,
     10- Crystal Methods, etc. 


    • The most widely adopted agile methods are Scrum and XP. 
    • Scrum (with or without combination with XP) is now applied in 74% of agile implementations 
    ]]>     2020-02-28 20:25:15 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452229808     Agile Core Principles: soa142812222 https://padlet.com/soa142812222/brdn5gzi557/wish/452230614 1-  Highest priority is to satisfy the customer through early and continuous delivery of valuable software
    2-Welcome changing requirements, even late in development
    3- Deliver working software 
    4- Business people and developers must work together daily throughout the project
    5- Build projects around motivated individuals]]>     2020-02-28 20:26:50 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452230614     Key practices of XP include the following: m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452233288
  • A team of five to ten programmers work at one location with customer representation onsite. 
  • Development occurs in frequent builds or iterations 
  • Requirements are specified as user stories 
  • Programmers work in pairs, follow strict coding standards, and do their own unit testing. Customers participate in acceptance testing. 
  • Requirements, architecture, and design emerge over the course of the project. 

    • ]]>     2020-02-28 20:32:14 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452233288     scrum m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452235055
  • Work is done in “sprints,” which are time boxed iterations of a fixed 30 days or fewer duration. 
  • Work within a sprint is fixed. Once the scope of a sprint is committed, no additional functionality can be added, except by the development team. 
    • ]]>     2020-02-28 20:36:03 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452235055     m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452237000 A Scrum Master mentors the empowered, self-organizing, and self- accountable teams that are responsible for delivery of successful outcomes at each sprint.

    A product owner plays the role of the customer proxy.

    A daily stand-up meeting is a primary communication method. 



    ]]>     2020-02-28 20:40:00 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452237000     Agile m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452241620 Resources and date are fixed

    requirements are estimated 

    (good)]]>     2020-02-28 20:50:08 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452241620     The value of any marketable feature decreases over time. m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452243358 2020-02-28 20:53:59 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452243358 Vision m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452423331 The system vision is a joint vision of the system agreed upon by all active stakeholders 


    ]]>     2020-02-29 17:54:33 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452423331     Vision characteristics: 1-Big picture 2-Abstract - vision purpose: 1-Agreement on what this project is about 2-Easy communication with stakeholders m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452423960 2020-02-29 17:58:05 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452423960 Example of Vision Statement template m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452425210
  • For [target customer] 
  •  Who [statement of the need or opportunity] 
  • The [product name] 
  •  Is [a product category] 
  •   That [key benefit, compelling reason to buy or use] 
  •   Unlike [primary competitive alternative, current system, or current business process], 
  •  Our product [statement of primary differentiation and advantages of new product] 


    • for examples read slides 6 and 7
    from lecture 4

    ]]>     2020-02-29 18:06:10 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452425210     m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452427350 Each software-intensive system is embedded within a "system context" that contains the requirement sources and strongly influences the definition of the system requirements.]]> 2020-02-29 18:21:17 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452427350 m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452427507
  • The vision and the system context are thus the two essential inputs for the RE process 
  • The main goal of RE is to:
    "establish a vision within an existing context" 

    • ]]>     2020-02-29 18:22:19 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452427507     Software-intensive systems are always embedded in environment m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452428295 environment
    Technologies, business processes, existing software components, people, laws, etc.]]>     2020-02-29 18:27:35 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452428295     System environment significantly influences requirements for the system m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452428435  A wrong assumption about the behavior of an external system will most likely lead to an incorrect definition of the requirement specifying interaction with the external system.]]> 2020-02-29 18:28:38 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452428435 m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452430904 The system context is the part of the system environment that is relevant for the definition as well as the understanding of the requirements of a system to be developed.]]> 2020-02-29 18:42:55 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452430904 m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452431069 The system boundary separates the system to be developed from its environment, i.e., it separates the part of the reality that can be modified or altered by the development process from aspects of the environment that cannot be changed or modified by the development process. 

    ]]>     2020-02-29 18:43:57 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452431069     m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452431131 The context boundary separates the relevant part of the environment of a system to be developed from the irrelevant part, i.e., the part that does not have to be considered during requirements engineering. 

    ]]>     2020-02-29 18:44:27 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452431131     Grey Zone between the System and the Context m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452432637 During requirements engineering, the system boundary as well as the interfaces are typically unstable (that you can decide is a part of system or part of context)]]> 2020-02-29 18:54:16 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452432637 read lecture 4 m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452434239 17
    and 20
    and 32 to 34]]>     2020-02-29 19:05:24 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452434239     Use goals and scenarios to check whether specific aspects of the environment are relevant for the system or not. If an aspect is relevant, it should affect at least one goal or one scenario. m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452436385 2020-02-29 19:20:31 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452436385 Requirements depend on the context m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452436597 may be true or false]]> 2020-02-29 19:22:11 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452436597 System Context: Four Facets m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452437288
    1- Subject facet: Objects and events relevant for the system.

    2- Usage facet: Aspects concerning the usage by people or other systems.
     
    3- IT system facet: Objects and elements of the IT system environment of the system

    4- Development facet: Aspects concerning the development process of the system 


    examples lecture 4 slides 24 and 25]]>     2020-02-29 19:27:34 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452437288     Three RE Core Activities m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452438507 1- Elicitation (content dimension)
    2- Negotiation (agreement dimension)
    3- Documentation (documentation dimension)

    for more details lecture 4 slide 28 

    ]]>     2020-02-29 19:36:36 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452438507     Two Cross Sectional Activities m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452439819 1- Validation
    2- Management

    ]]>     2020-02-29 19:45:18 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452439819     The three requirements artefacts types m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452443243 1- goals
    2- Scenarios 
    3- solution-oriented

    for more details lecture 4 slides 35 to 37
    ]]>     2020-02-29 20:09:17 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452443243     read lecture 5 m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452446843 7 to 9
    and 22
    and 27
    and 28
    and 30 to 34
    Important to read from 35 to the end (GRL)    ]]>     2020-02-29 20:36:17 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452446843     Goal Dependencies m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452449216 Goals can have the following types of dependencies between each other: 
     Requires
     Support
     Obstruction
      Conflict 
     Equivalence 

    for more details and examples lecture 5 slides 13 to 18

    ]]>     2020-02-29 20:53:34 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452449216     An “obstruction” dependency cannot exist between goals that are part of an AND-decomposition m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452450961 2020-02-29 21:06:38 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452450961 Context changes affect goal dependencies m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452451101 Example:
     Change of a data protection law in a country may prohibit the electronic localization of a car]]>     2020-02-29 21:07:33 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452451101     Goals can be documented: m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452451561  Using unstructured natural language.

     Using templates (structured)

     Using dedicated goal modeling languages. ]]>     2020-02-29 21:10:50 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452451561     Documenting Goals using unstructured natural Language m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452451776 Unstructured approach implies specifying goals one after the other in free text, without any specific rules. ]]> 2020-02-29 21:12:29 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452451776 Documenting Goals using templates (structured) m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452451942 Template-based documentation of goals offers significant advantages. ]]> 2020-02-29 21:14:00 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452451942 apply the following steps to weaken the restrictions: m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452454871
  • Elicit the actual, solution/constraint-free super-goal that is behind the required solution by asking “why” questions. 
  • Try to identify viable solution alternatives for the super- goal. 
  • Document the identified, alternative solutions as sub-goals of the solution-free super-goal using an OR-decomposition. 

    • ]]>     2020-02-29 21:36:03 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452454871     Model-based goal documentation m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452455294  helps understanding and communicating goals
     complements template-based documentation


    Goal modeling method consists of language, rules, guidelines and management practices ]]>     2020-02-29 21:39:25 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452455294     URN Formalizes and integrates two notations: m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452536948  Goal-oriented Requirement Language (GRL)

     Use Case Maps (UCMs) for expressing scenarios ]]>     2020-03-01 09:34:30 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452536948     URN models can be used to specify and analyze various types of (proposed or evolving) reactive systems, business processes, and telecommunications standards m_alqadi779 https://padlet.com/soa142812222/brdn5gzi557/wish/452537405 2020-03-01 09:38:39 UTC https://padlet.com/soa142812222/brdn5gzi557/wish/452537405