Test 1 Updated Flashcards

Question

What is ASD?

Answer 1

Adaptive software dev = technique for building complex software and systems. - Speculation - initiation state - adaptive cycle planning is conducted - Collaboration - Learning

Answer 2

Dynamic Systems Development Method provides a framework for building and maintaining systems through the use of incremental prototyping in a controlled project environment. Latest version of RAD – role of “keeper” of the method. DSDM life cycle: -Feasibility study -Business study -Functional model iteration -Design and build iteration -Implementation

Answer 3

Requirements are prioritized using this ranking: M – Must have requirements S – Should have if at all possible C – Could have but not critical W – Won’t have this time, but potentially later

Answer 4

- Create user stories and convert into product 'backlog' or 'wish list' to make this application successful - Identify which specific stories should be good or bad - remove from wish list - Identify roles - Prioritize backlog - and breakdown large tasks (if any) - Provide estimates of release of each task - Create release backlog and divide them into sprints - Each member updates the amount of work completed and goal satisfaction on a daily basis. As a team, daily performance is stored and remaining work can be measured.

Answer 5

-Product owner – to make sure right features get into the backlog. Set the direction. -Scrum Master (project manager) – identify project tools, organize team, setup meetings, etc. -Developer – build the system -Testers – Test the application -Customers – use it -Executive team

Answer 6

The goal of Sprints (Sprint 1, Sprint 2, … Sprint n) is to make ‘Release Backlog’ items into ship-ready state. All features must be 100% complete.

Answer 7

-It is extremely important to monitor the Sprint performance. For example, with a chart called Burndown Chart. -The Burndown Chart is the reason for Sprint’s popularity and success. Includes: Work Remaining Vs Time.

Answer 8

Resource limited method where primary goal is to deliver working software and secondary goal is setting up the next target. Comprised of: Crystal Clear, Crystal Yellow, Crystal Orange characteristics. Driven by factors: Team size, system criticality, project priorities

Answer 9

Feature Driven Development | A "feature" is a client-valued function that can be implemented in a givem time.

Answer 10

Agile Modeling - Model with a purpose - Use multiple models - Content is more important - Know the models and tools - Adapt locally - within a team

Answer 11

Function deployment determines the value (as perceived by the customer) of each function required of the system

Answer 12

Identifies data objects and events

Answer 13

Examines the behavior of the system

Answer 14

Determines the relative priority of requirements

Answer 15

- A statement of need a feasibility - A bounded statement of scope for the system or product - A list of customers, user, and other stakeholders who participated in requirements elicitation - A description of the system's technical environment - A list of requirements and the domain contraints that apply to each - A set of usage scenarios that provide insight into the use of the system or product under different operating conditions - Any prototypes developed to better define requirements

Answer 16

-Scenario-based elements: -Functional: Processing narratives for software functions Use-case: Descriptions of the interaction between an "actor" and the system Class-based elements: Implied by scenarios Behavioral Elements: State diagram Flow-oriented elements: Data flow diagram

Answer 17

Computer Aided Software Engineer is a category of software that provides a development environment for programming teams.

Answer 18

- Summarizing initial requirements - Developing flow diagrams - Scheduling development tasks - Preparing documentation - Developing program code, Debugging environments, verification and validation - Graphical modeling tools (E/R modeling, object modeling etc.) - Analyze code for complexity, modularity, performance - Project management. Manage plans, task assignments, scheduling

Answer 19

A collection of user scenarios that describe the thread of usage of a system. Each scenario is described from the point of view of an "actor" - a person or device that interacts with the software in some way

Answer 20

◦Who is the primary actor, the secondary actor (s)? ◦ What are the actor’s goals? ◦ What preconditions should exist before the story begins? ◦ What main tasks or functions are performed by the actor? ◦ What extensions might be considered as the story is described? ◦ What variations in the actor’s interaction are possible? ◦ What system information will the actor acquire, produce, or change? ◦ Will the actor have to inform the system about changes in the external environment? ◦ What information does the actor desire from the system? ◦ Does the actor wish to be informed about unexpected changes?

Answer 21

A class diagram describes the member variables and functions that a class within the system will need.

Answer 22

Walks through all possible states for the system, the relevant variables values in those states, as well as the relevant actions available

Answer 23

Allows the modeler to represent the flow of activitied described by the use-case and at the same time indicate which actor (if there are multiple) or analysis class has responsibility for the action described by an activity rectangle.

Answer 24

-Is each requirement consistent with the overall objective for the system/product? -Have all requirements been specified at the proper level of abstraction? That is, do some requirements provide a level of technical detail that is inappropriate at this stage? -Is the requirement really necessary or does it represent an add-on feature that may not be essential to the objective of the system? -Is each requirement bounded and unambiguous? -Do any requirements conflict with other requirements? -Is each requirement achievable in the technical environment that will house the system or product? -Is each requirement testable, once implemented? -Does the requirements model properly reflect the information, function and behavior of the system to be built. -Has the requirements model been “partitioned” in a way that exposes progressively more detailed information about the system. -Have requirements patterns been used to simplify the requirements model. Have all patterns been properly validated? Are all patterns consistent with customer requirements?

Answer 25

- Define the domain to be investigated. - Collect a representative sample of applications in the domain: Research your case + competitors - Analyze each application in the sample. - Develop an analysis model for the objects.

Answer 26

- Scenario-based elements (Use-case diagrams, Use cases - test, Activity diagrams, swim line diagrams) - Class based elements (class diagrams, analysis packages, CRC models, collaboration diagrams) - Flow-oriented elements (Data-flow diagrams, Control flow diagrams, processing narratives) - Behavioral elements (State diagrams, sequence diagrams)

Answer 27

Represents how data objects are transformed at they move through the system A data flow diagram (DFD) is the diagrammatic form that is used Considered by many to be an ‘old school’ approach, flow-oriented modeling continues to provide a view of the system that is unique—it should be used to supplement other analysis model elements

Answer 28

Represented as a square in a DFD, a producer or consumer of data, such as a person, a device or a sensor.

Answer 29

Represented as a circle in a DFD, a process is a data transformer which changes input to output. For example, computing taxes, determining area, formatting a report, or displaying a graph.

Answer 30

Represented as an arrow (with text) in a DFD. Data flows through a system beginning as input and being transformed into output. I.e. base and height flowing into a process that computes a triangles area, and the area data flowing out of the process as output.

Answer 31

Represented as two horizontal bars (like an equal sign with text in between). Represents data being stored for later use

Answer 32

-all icons must be labeled with meaningful names -the DFD evolves through a number of levels of detail -always begin with a context level diagram (also called level 0) -always show external entities at level 0 -always label data flow arrows -do not represent procedural logic

Answer 33

-each bubble (process) is refined until it does just one thing -the expansion ratio decreases as the number of levels increase -most systems require between 3 and 9 levels for an adequate flow model -a single data flow item (arrow) may be expanded as levels increase (data dictionary provides information)

Answer 34

Represents “events” and the processes that manage events An “event” is a Boolean condition that can be ascertained by: ◦ listing all sensors that are "read" by the software. ◦ listing all interrupt conditions. ◦ listing all "switches" that are actuated by an operator. ◦ listing all data conditions. ◦ recalling the noun/verb parse that was applied to the processing narrative, review all "control items" as possible CSPEC inputs/outputs.

Answer 35

External entities (e.g., other systems, devices, people) that produce or consume information to be used by a computer-based system. Things (e.g, reports, displays, letters, signals) that are part of the information domain for the problem. Occurrences or events (e.g., a property transfer or the completion of a series of robot movements) that occur within the context of system operation. Roles (e.g., manager, engineer, salesperson) played by people who interact with the system. Organizational units (e.g., division, group, team) that are relevant to an application. Places (e.g., manufacturing floor or loading dock) that establish the context of the problem and the overall function of the system. Structures (e.g., sensors, four-wheeled vehicles, or computers) that define a class of objects or related classes of objects.

Answer 36

Class Responsibility Collaborator modeling. Analysis classes have "responsibilities" which are the attributes and operations encapsulated by the class Analysis class collaborate with one another -Collaborators are those classes that are required to provide a class with the information needed to complete a responsibility. ◦ In general, a collaboration implies either a request for information or a request for some action.

Answer 37

Business functions to be developed -All data required for these business functions -Business rules determining data behavior, constraints, limits, relationships, and life-cycle -Business function flow -Identify other related business systems -Collaboration with other external and internal business systems -Existing data that may have to be converted -Opportunities for re-engineering Preliminary transition plan -Security requirements -Technical architectures that maximize opportunities for appropriate sharing of information -Architectural issues such as network and systems capacity planning -Contingency planning

Answer 38

-Do surveys of the marketplace and indicate availability of similar products that would address the majority of your business problems. -Determine product compatibility with the current technical environment and standards (includes security, network, database, desktop tools, middleware, and application software delivery issues). -Analyze the full life-cycle cost of a buy-versusbuild decision, including customization cost. -Determine the availability of internal resources to build a system. -Identify the contract resources available to augment staff to build a system. -Analyze the time-frame involved in buying versus building a system.

Answer 39

-Determine how technical and functional upgrades will be accomplished. -Determine desktop and server hardware, and need to upgrade or change end-user desktop computers. -Determine timing and strategy for backing up data. -Determine resources to support ongoing operations addressing application and hardware maintenance. -Develop a communication plan

Answer 40

-Acceptable approaches -Acceptable technologies and general architectures -Opportunities for re-engineering -Refinement of resource needs (people, money, environment) -Unacceptable approaches -Unacceptable technologies and general architectures -Risks

Answer 41

The software architecture of a system is the set of structures needed to reason about the system, which comprise system elements, relations among them, and properties of both.

Answer 42

1. An overview, the overall shape 2. How it fits in with its environment 3. How it meets its purposes 4. Its visual impact 5. Its small details 6. The decisions that go into the design

Answer 43

The architecture is not the operational software. Rather, it is a representation that enables a software engineer to: (1) analyze the effectiveness of the design, its stated requirements, (2) consider architectural alternatives at a stage when making design changes is still relatively easy, and (3) reduce the risks associated with the construction of the software.

Answer 44

1. Software components are emphasized 2. Components range from modules and classes to databases and middleware 3. Properties of components: what is necessary to understand how the components interact

Answer 45

An implementation-specific skeletal infrastructure for design work. It provides a generic structure and behavior for a family of software abstractions, and specifies their collaboration and use within a given domain.

Answer 46

1) a set of components (e.g., a database, computational modules) that perform a function required by a system, 2) a set of connectors that enable “communication, coordination and cooperation” among components, 3) constraints that define how components can be integrated to form the system, and 4) semantic models that enable a designer to understand the overall properties of a system by analyzing the known properties of its constituent parts.

Test 1 Updated Flashcards

(70 cards)