System analysis and design chapter 1-4 exam |148 questions and answers

Information system A set of interrelated components that collects processes stores and provides as output the information needed to complete business task . Always includes people who operate the system and carry out some of the work Systems analysis Those system development activities that enable a person to understand and specify what the new system should accomplish Systems design System development activities that enable a person to describe in detail how the resulting information system will actually be implemented Project A planned undertaking that has a beginning,end, and produces end results SDLC System development life cycle System development life cycle A framework that identifies all the activities required to research, build, deploy, and often maintain an information system System development process Or system development methodology, a set of comprehensive guidelines for carrying out all the activities of each core processor of the SDLC Name the SDLC core processes 1. Identify the problem and obtain approval 2. Plan and monitor the project 3. Discover and understand the details of problem or need 4. Design system components 5. Build, test,and integrate system components 6. Complete system tests and deploy the solution 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 Subsystem An identifiable and fully functional part of a complete system The planning process for an iteration consists of three steps: -Identify the tasks required for the iteration -Organize and sequence these tasks into a schedule -Identify required resources (especially people) and assign people to tasks WBS Work breakdown structure What is the WBS After tasks of an iteration are identified, they are compiled and organized into a document by order of importance, this includes estimates of how long each task will take. Iteration schedule Tasks taken from the WBS and placed them on day-by-day sequence. Two core process 1 activities (called pre-project activities) -Identify the problem and document the objective of the solution system -Obtain approval to commence the project System Vision Document Document that shows the problem description, system capabilities, and business benefits. Three core process 2 activities -Determine the major components (functional areas) that are needed -Define the iterations and assign each functional area to an iteration -Determine team members and responsibilities Core process 3 activities: -Do fact-finding tasks to understand the requirements -Develop a list of use cases and a use case diagram -Develop a list of classes and a class diagram, define user experience with sketches of screens and reports needed for each use case Use case a document showing a case or situation where the system is used. ex/USE CASE: Look up supplier, DESCRIPTION: using suppler name, find supplier information and contacts Domain classes Identifies the things in the real world that the system needs to know about and keep track of. To find domain classes, we look for all objects or things that a system uses or captures. EX/Object class: Supplier Attributes: Supplier name, address, description, comments Domain class diagram: a visual diagram of domain classes, their attributes, and their associations with other classes Use case description a method for documenting details of a use case, to document interactions between the user and the system activity diagram a UML diagram that shows all the steps within the use case, to document interactions between the user and the system and the sequential flow of the activities ex/Purchasing agent: start-enter supplier name- ex/Tradeshow system: return supplier information Use case diagram Document that graphically portray use cases and users involved in the subsystem ex/How an agent would use the system vs. how a manager may use the system Core process 4 activities: -Design the schema (database structure) -Designt he system's high-level structure OOP Object-Oriented Programming Design class diagram document that identifies the software classes needed for the system Core process 5 activities: -create detailed design -program the subsystem components Core process 6 activities: Final testing Two types of final testing (core process 6) -Functional testing- test of all user functions done by quality assurance team -User acceptance tests- completed by users who test both correctness of system and its "fitness" to accomplish the business reqs technology architecture a set of computing hardware, network hardware, and topology and system software(software applications) employed by an organization Systems analysis (Core process 3) activities -Gather detailed information -Define requirements -Prioritize requirements -Develop user-interface dialogs -Evaluate requirements with users Defining requirements: The analyst creates models to __ to record requirements, review the models with users, and others, and refines and expands the models to reflect new or updated information Scope creep When system requirements expand as users make more suggestions A __ developed in an early iteration can be expanded in later iterations to become a fully functioning part of the system. user-interface prototype System requirements All the activities the new system must perform or support and the constraints that the new system must meet (functional and non-functional) Functional requirements The activities the system must perform to support the user's work Non-functional requirements Required system characteristics other than the activities it must perform or support FURPS An acronym that stands for functional, usability, reliability, performance, and security requirements Usability requirements The requirements for operational characteristics related to users such as the user interface, related work procedures, online help, and documentation Reliability requirements The requirements that describe system dependability Generally, analysts divide system requirements into two categories Functional and nonfunctional requirements Performance requirements The requirements that describe operational characteristics related to measures of workload such as throughput and response time Security requirements The requirements that describe how access to the application will be controlled and how data will be protected during storage and transmission FURPS+ An extension of FURPS that includes design constraints as well as implementation, system interface, physical and supportability requirements Stakeholders Persons who have an interest in the successful implementation of the system Internal stakeholders Persons within the organization who interact with the system or have a significant interest in its operation or success External stakeholders Persons outside the organization's control and influence who interact with the system or have a significant interest in its operation or success