System Analysis and Design Final Exam guide questions fully solved(verified for accuracy).

Information System A set of interrelated components that collect, process, store, and provide as output the information needed to complete business tasks Systems Analysis Those system development activities that enable a person to understand and specify what the new system should accomplish Systems Design Those system development activities that enable a person to describe in detail how the resulting information system will actually be implemented System Development Life Cycle (SDLC) A framework that identifies all the activities required to research, build, deploy, and often maintain an information system 1. Identify the problem and obtain approval 2. Plan and monitor the project 3. Discover and understand details 4. Design system components 5. Build, test, and integrate system components 6. Complete system tests and deploy the solution What are the core processes of the SDLC? Agile Development An information system development process that emphasizes flexibility and rapid response to anticipate new and changing requirements during development Iterative Development An approach to system development in which the system is "grown" piece by piece through multiple mini-projects called iterations 1. Gather detailed information 2. Define requirements 3. Prioritize requirements 4. Develop user-interface dialogs 5. Evaluate requirements with users What are the activities of system analysis? (Pg. 43) Functional Requirements The activities the system must perform to support the users' work Nonfunctional Requirements Required system characteristics other than the activities it must perform or support Stakeholders Persons who have an interest in the successful implementation of the system 1. Interviews 2. Questionnaires 3. Documentation, input and output reviews 4. Process observation and documentation 5. Researching vendor solutions 6.Active user comments and suggestions What are some information-gathering techniques? Model Representation or abstraction of some aspect of a system Unified Modeling Language (UML) A standard set of information system model constructs and notations defined by the Object Management Group User Story One short sentence in the everyday language of the end user that states what a user does as part of his or her work Use Case An activity that the system performs in response to a request by a user User Goal Technique A technique to identify use cases by determining what specific goals or objectives must be completed by the system for the user Event Decomposition Technique A technique to identify use cases by determining the business events to which the system must respond Event Something that occurs at a specific time and place, can be precisely identified, and must be remembered by the system Use Case Diagram The UML model used to illustrate use cases and their relationships to actors Problem Domain The specific area (domain) of the user's business need that is within the scope of the new system Noun Technique A technique used to identify things in the problem domain by finding and classifying the nouns in a dialog or description Data Entities The term used in ERD modeling to describe things about which the system needs to store information Domain Classes Classes that describes objects from the problem domain Use Case Description A textual model that lists and describes the processing details for a use case System Sequence Diagram (SSD) A diagram showing the sequence of messages between an actor and the automated part of the system during a use case or scenario Entity-Relationship Diagram (ERD) A diagram consisting of data entities, their attributes, and their relationships CRUD Technique An acronym for Create, Read/Report, Update, and Delete; a technique to validate or refine use cases Security Controls Controls that protect the assets of an organization from all threats, with a primary focus on external threats Integrity Controls Controls that reject invalid data inputs, prevent unauthorized data outputs, and protect data and programs against accidental or malicious tampering Access Control A control that limits a user's ability to access resources, such as servers, files, Web pages ,application programs, and database tables Application Software Software that performs user- or business-specific tasks and is typically constructed as an app or Web-based application System Software Software, such as operating systems and Web server software, that works behind the scenes to support application software and control or interact with hardware or software resources Protocol A set of languages, rules, and procedures that ensure accurate and efficient data exchange and coordination among hardware and software components Software as a Service (SaaS) A software delivery model similar to a utility, in which application software is accessed via the Internet without locally installed programs Interoperability The ability of a component or system to interact with other components or systems System Architecture Structure of components and interactions. Captures a vision of the general appearance. Includes built-in decisions driven by requirements Three-layer Architecture Components split into independent modules Layers: - View - user interface - Logic - Program logic implementing functions - Data - Functions that access data User Experience (UX) All aspects of a person's interaction with a software application, including actions, responses, perceptions, and feelings User Interface (UI) The set of inputs and outputs that the user interacts with to invoke the functions of an application Usability The degree to which a system is easy to learn and use Metaphors Analogies between features of the user interface and aspects of physical reality with which users are familiar Human-Interface Objects (HIOs) Icons and other objects on a screen that can be manipulated by the user and cause some action to occur Storyboarding Sequence of sketches of the display screen during a dialogue Discoverability A feature of the user interface that provides clues to help the users uncover hidden features