100% de satisfacción garantizada Inmediatamente disponible después del pago Tanto en línea como en PDF No estas atado a nada
logo-home
Software Engineering Exam 2- Questions Answered Exactly (New version ) $8.29
Añadir al carrito

Examen

Software Engineering Exam 2- Questions Answered Exactly (New version )

 0 veces vendidas
  • Grado
  • Software Engineering Exm 2
  • Institución
  • Software Engineering Exm 2

Software Engineering Exam 2- Questions Answered Exactly (New version ) Software architecture - Answers a set of high-level decisions made during the development and evolution of a software system. A decision is "architectural" if, given the current level of system scope, the decision must be made ...

[Mostrar más]

Vista previa 2 fuera de 8  páginas

  • 27 de diciembre de 2024
  • 8
  • 2024/2025
  • Examen
  • Preguntas y respuestas
  • Software Engineering Exm 2
  • Software Engineering Exm 2
avatar-seller
Software Engineering Exam 2- Questions Answered Exactly (New version 2024-2025)

Software architecture - Answers a set of high-level decisions made during the development and
evolution of a software system. A decision is "architectural" if, given the current level of system scope,
the decision must be made by considering the current scope level

Responsibilities - Answers actors have their responsibilities and seek the system's assistance in
managing those responsibilities

Goals - Answers to carry out its responsibilities, an actor sets goals, which are time and context-
dependent

Action - Answers an action is the triggering of an interaction with the system-to-be

Actor - Answers can be a person or another system which interacts with out system-to-be.

Initiating actor - Answers also called primary actor, or user: initiates the use case to realize a goal, which
depends on the actor's responsibilities and the current context

Participating actor - Answers also called secondary actor: participates in the use case but does not
initiate it; there are two subcategories: supporting actor (helps the system-to-be to complete the use
case-that is, our system-to-be initiates the supporting actor) and offstage actor (passively participates in
the use case, i.e., neither initiates nor helps complete the use case, but maybe notified about some
aspect of it)

Use case - Answers a usage scenario for an external entity, known as actor, and the system-to-be. A use
case represents an activity that an actor can perform on the system and what they system does in
response. It describes what happens when an actor disturbs out system from its "stationary state" as the
system goes through its motions until it reaches a new stationary state;; are text stories that detail
exactly what happens when an actor attempts to obtain a service from the system

Use case diagram - Answers sums up the actors, use cases, and their relationships

Two use-case categories distinguished: - Answers "first-" (use cases represent meaningful services
provided by the system to an actor) vs. "second tier" (use cases represent elaborations or sub-services
of the main services)

The two stereotypical - or cliche types of relationship are: - Answers <<extend>> - optional extensions of
the main case

<<include>> - required subtasks of the main case

Alternate scenarios or extensions in a use case can result from: - Answers - Inappropriate data entry,
such as the actor making a wrong menu-item choice (other than the one he/she originally intended), or
the actor supplies an invalid identification

, - System's inability to respond as desired, which can be a temporary condition or the information
necessary to formulate the response may never become available

User acceptance test case - Answers at the time of writing detailed use cases, we also write the
corresponding user acceptance tests.....user acceptance test case is a detailed procedure that fully tests
a use case or one of its flows of events.

System sequence diagram - Answers represents in a visual form a usage scenario that an actor
experiences while trying to obtain a service form the system

Business process risk - Answers the chance of something happening that will have an impact on the
process objectives, such as financial or reputational damage, and is measured in terms of likelihood and
consequence

Misuse cases - Answers

Associations - Answers describe who needs to work together and why, not how they work together

Optimal design - Answers to derive a "good" design

Good software designs are characterized with: - Answers -Short communication chains between the
objects

-Balanced workload across the objects

-Low degree of connectivity (associations) among the objects

Design heuristics - Answers used to achieve "optimal" designs can be roughly divided as: Bottom-up
(inductive) approaches that are applying design principles and design patterns locally at the level of
software objects. and Top-down (deductive) approaches that are applying architectural styles globally,
at the system level, in decomposing they system into subsystems (micro-level design)

Responsibility-driven design (RDD) - Answers a popular approach to micro-level design. We know the
types of responsibilities that objects can have:

Type 1 responsibilitiy - Answers (knowing): memorizing data or references, such as data values, data
collections, or references to other objects, represented as a property

Type 2 responsibility - Answers (doing) : performing computations, such as data processing, control of
physical devices, etc., represented as a method

Type 3 responsibility - Answers (communicating): Communicating with other objects, represented as
message sending (method invocation)

Important design principles at the local, objects level include: - Answers -Expert Doer principle: that who
knows should do the task; helps shorten the communication chains between the objects

Los beneficios de comprar resúmenes en Stuvia estan en línea:

Garantiza la calidad de los comentarios

Garantiza la calidad de los comentarios

Compradores de Stuvia evaluaron más de 700.000 resúmenes. Así estas seguro que compras los mejores documentos!

Compra fácil y rápido

Compra fácil y rápido

Puedes pagar rápidamente y en una vez con iDeal, tarjeta de crédito o con tu crédito de Stuvia. Sin tener que hacerte miembro.

Enfócate en lo más importante

Enfócate en lo más importante

Tus compañeros escriben los resúmenes. Por eso tienes la seguridad que tienes un resumen actual y confiable. Así llegas a la conclusión rapidamente!

Preguntas frecuentes

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.

100% de satisfacción garantizada: ¿Cómo funciona?

Nuestra garantía de satisfacción le asegura que siempre encontrará un documento de estudio a tu medida. Tu rellenas un formulario y nuestro equipo de atención al cliente se encarga del resto.

Who am I buying this summary from?

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

Will I be stuck with a subscription?

No, you only buy this summary for $8.29. You're not tied to anything after your purchase.

Can Stuvia be trusted?

4.6 stars on Google & Trustpilot (+1000 reviews)

45,681 summaries were sold in the last 30 days

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

Empieza a vender
$8.29
  • (0)
Añadir al carrito
Añadido