Chapter 1 1. What is the difference between an information system and a computer application? An information system is a set of interrelated computer components that collects, processes, stores and provides output of the information for business purposes anda computer application is a computer software program that executes on a computer device t o carry out a specific function or set of related functions.
2. What is the purpose of systems analysis? the process of studying a procedure or business in order to identify its goals and purposes purposes and and create systems systemsand and procedures that will achieve them in an efficient way systems are created to solve problems. We need to see all sides of a problem to come up with an acceptable solution. Analysis involves studying the system and seeing how they interact with the entities outside as well as inside the system. We then come out with detailed specifications of what the system will accomplish based on the user requirements. Systems design will take the requirements and analysis into consideration and come out with a high level and low level design that will form the blue print to the actual solution to the problem in hand.
3.
What is the difference between systems analysis and systems design?
Performed by a Systems Analyst System Specification: everything about what the the proposed system will do, nothing about how it it is to be be built The audience is Sponsoring users Chief programmer (or Software Architect or Lead developer
Performed by Chief programmer (or Software architect or Lead developer) System Architecture: everything about how it it has to be built - platform choice, database design, program design, user interface design, etc. , in order to meet the system specification
The audience is Programmers and technical specialists
4. What is a project? what is project project:: a piece of planned work or an activity that is finished over a period of time 5. What are the six core processes for software systems development?
Identify problem and obtain approval. Plan and monitor the project. Discover and understand details. Design system components. Build, test, and integrate system components. Complete system tests and deploy solution.
6. There are following six phases in every Softwar e development life cycle model:
Requirement gathering and analysis. Design. Implementation or coding. Testing. Deployment. Maintenance. 7. What is meant by Agile Development?
Agile development is an alternative to traditional project management where emphasis is placed on empowering people to collaborate and make team decisions in addition to continuous planning, continuous testing and continuous integration.
8. What is the purpose of a System Vision Document? A Vision Document is a document that describes a compelling idea or values or future state for a particular organization, product or service. It defines the stakeholders view of the product/service to be developed, specified in terms of the stakeholders key needs and features. 9. What is the difference between a system and a subsystem? System is a combination of parts working together to acc omplish a goal, and a subsystem is a complete system that is an integral part of a larger system. A subsystem is simply a portion of the overall system. Based on the list of System Capabilities, the project team identifies these functional subsystems: ■ Supplier Information subsystem ■ Product Information subsystem The Supplier Information subsystem will c ollect and maintain information about the manufacturers or wholesalers and the contract people that work for them. The Product Information subsystem will capture information about the various products, including detailed descriptions and photographs.
10. What is the purpose of a Work Breakdown Structure?
The main purpose of a WBS is to reduce complicated activities to a collection of tasks. This is important for the project manager because she can oversee the tasks more effectively than the complex activities. Tasks must be measurable and independent, with clearly defined limits.
11. What information is provided by use cases or a use c ase diagram? UML Use Case Diagrams. Use case diagrams are usually referred to as behavior diagrams used to describe a set of actions ( use cases) that some system or systems (subject) should or can perform in collaboration with one or more external users of the system (actors).
Used to gather requirements of a system.
Used to get an outside view of a system.
Identify external and internal factors influencing the system.
Show the interacting among the requirements are actors.
12. What information is provided by a class diagram?
static structure diagram that describes the structure of a system by showing the system's classes, their attributes, operations (or methods), and the relationships among objects. Used for
Analysis and design of the static view of an application.
Describe responsibilities of a system.
Base for component and deployment diagrams.
Forward and reverse engineering
13. How does an activity diagram help in user-interface design?
Activity diagram is basically a flow chart to represent the flow form one activity to another activity. The activity can be described as an operation of the system.
Following are the main usages of activity diagram:
Modeling work flow by using activities.
Modeling business requirements.
High level understanding of the system's functionalities.
Investigate business requirements at a later stage.
14.
What new information is provided in a design class diagram (more than a class
diagram)? Includes View Layer Classes Domain Layer Classes And methods
15. What is the purpose of user acceptance testing? User acceptance testing (UAT) is the last phase of the software testing process. During UAT, actual software users test the software to make sure it can handle required tasks in real-world scenarios, according to specifications.
Chapter 2 16. Systems analysis five activities
17.
Gather detailed information
Data from future users, current users, and previous users Information from people who’ve built/worked on similar systems Study existing systemsiv.Data on how the system should work and what other systems it will interact/in-terface withb. Define requirements Gather information from users and documents Create mock-ups, models, demos, and previews of how the s ystem should look according to the requirements. Prioritize requirements Establish which requirements are crucial for the system Categorize requirements based on need, function, and importanced. Develop user-interface dialogs Use proto-types, models and mockups to evaluate what is b est for the user andwhat the client wants. Evaluate requirements with users After the above four, run everything through with the user/client to evaluate andensure everything is what the client wants 18. What are three types of models?
Textual model– something written down, des cribed
Graphical models– diagram, schematic
Mathematical models– formulas, statistics, algorithms
19. What is the difference between functional requirements and nonfunctional requirements?Functional requirements are the activities the system must perform. The nonfunctional requirements are the other system characteristics.
20. What types of stakeholders should you include in fact finding?You should include internal, external, operational, and executive
21. What is the purpose of an activity diagram.The purpose is to describe user (or system) activities, the person who does each activity, and the sequential flow of these activities.
Chapter 3
What is a use case?
A use case is an activity that the system performs as a result of some event or action by a user
What are the two techniques used to identify use cases?
User goal technique and the event decomposition technique
Describe the user goal technique for identifying use cases.
The user goal technique is done by interviewing a user (or user role) to see what their work “goals” or objectives are. These are low level objectives to accomplish a piece of work or to complete a work procedure. The system then must have use cases to support each user goal.
Describe the event decomposition technique for identifying use cases.
Look at all of the business processes that result in some type of bu siness event. The business events are triggers that require system processing, e.g. that require use cases.
Why is the event decomposition technique considered more comprehensive than the user goal technique?
Event decomposition not only looks at user initiated events (the same as the user goal technique), but it also considers temporal events and state events. Hence it is more comprehensive. What is an event? Something that occurs at a specific time and place. It can be identified, and for purposes of systems analysis, the system must recognize it and capture some information from it or about it
What are the three types of events?
External event – usually from a user Temporal event – occurs at a point in time, or due to a time interval State event – a change of state or condition of some data within the system
Define an external event and then give an example that applies to a checking account system.
An external event is something that occurs external to the s ystem, and is trigger by a user action. An example might be that a user makes a direct deposit to his/her account.
Define a temporal event and then give an example that applies to a checking account system. A temporal event is one that occurs at a point in time. An example might be that at the end of the month interest (or monthly checking a ccount fee) is calculated and credited to the account What are the four operations that make up the CRUD acronym? C = Create R = Read or Report (output) U = Update D = Delete What is a brief use case description? A one or two sentence description of the use case and what it accomplishes. What is the purpose of UML use case diagrams?
Use case diagrams provide a graphical view of use c ases and the actors that invoke those usecases. They provide a nice overview of use cases.They can organize use cases together inmeaningful ways.
What is the «includes» relationship between two use cases?
The «includes» relationship is where one use case effectively uses the services of another usecase. It is as though one use case were embedded within another use case.
