Term
| Systems Development Life Cycle |
|
Definition
| Lifecycle that covers the overall pattern we follow when we design develop and implement. The type of methodology varies. We focused on the Object-Oriented systems approach using the RUP |
|
|
Term
|
Definition
| The fundamental process of understanding WHY an information system should be built and determining how the project team will go about building it. |
|
|
Term
|
Definition
| 1. Project Initiation 2. Project Management |
|
|
Term
|
Definition
| answers the questions: WHO will use the system, WHAT the system will do and WHERE and WHEN will it be used. |
|
|
Term
| Analysis Phase three steps |
|
Definition
| 1. Analysis Strategy, 2. Requirements Gathering, 3. System Proposal |
|
|
Term
|
Definition
| includes an analysis of the AS-IS SYSTEM and its problems, THEN ways to design the new TO-BE SYSTEM |
|
|
Term
|
Definition
| includes gathering information, ANALYSIS of the information, developing a SYSTEM CONCEPT to create a SET OF BUSINESS ANALYSIS MODELS to describe how the business will operate with the TO-BE SYSTEM. |
|
|
Term
|
Definition
| A SYSTEM PROPOSAL document is CREATED FROM ANALYSES, SYSTEM CONCEPT and MODELS. |
|
|
Term
|
Definition
| decides HOW the SYSTEM WILL OPERATE, in terms of the hardware, software, and network infrastructure; the user interface, forms and reports; and the specific programs, databases, and files that will be needed. |
|
|
Term
|
Definition
| Design Stage, Development of Architecture and Interface, Database and file specification, Program Design |
|
|
Term
|
Definition
| clarifies…WILL the SYSTEM be DEVELOPED … IN HOUSE, will be OUTSOURCED TO ANOTHER FIRM, or if EXISTING SOFTWARE PACKAGE IS BOUGHT. |
|
|
Term
|
Definition
| describes the HARDWARE, SOFTWARE, and NETWORK INFRASTRUCTURE to be used. |
|
|
Term
|
Definition
| specifies HOW USERS MOVE THROUGH SYSTEM and the FORMS and REPORTS that the system will use. |
|
|
Term
| Database and file specification |
|
Definition
| define exactly WHAT DATA will be STORED and WHERE it will be STORED. |
|
|
Term
|
Definition
| defines the programs that need to be written and exactly what each program will do. |
|
|
Term
| Deliverable of Design Phase |
|
Definition
| the SYSTEM SPECIFICATION to be handed to programmers for implementation. |
|
|
Term
|
Definition
| during which the system is actually built or purchased. NEEDS THE MOST ATTENTION - phase is the longest and most expensive. |
|
|
Term
| 3 steps of implementation |
|
Definition
| Construction, Installation, Support PlaN |
|
|
Term
|
Definition
| SYSTEM is BUILT and TESTED TO ENSURE IT PERFORMS AS DESIGNED. |
|
|
Term
|
Definition
| Process by which the OLD SYSTEM is TURNED OFF and NEW SYSTEM is TURNED ON. |
|
|
Term
|
Definition
| includes a formal or informal post-implementation review identifying major and minor changes needed for the system. |
|
|
Term
|
Definition
| to teach users how to use the new system and help manage the changes caused by the new system. |
|
|
Term
| What are the characteristics of Object-Oriented systems |
|
Definition
| a. Classes and Objects. b. Methods and messages |
|
|
Term
|
Definition
the general template used to define and create specific instance or objects.
_______ have attributes and methods. |
|
|
Term
|
Definition
| an instantiation of a class – that is a person, place or thing about which we want to capture information |
|
|
Term
|
Definition
| each object has attributes that describe information about the object and are used to represent relationships between objects |
|
|
Term
|
Definition
| of an object is defined by the value of its attributes and its relationships with other objects at a particular point in time |
|
|
Term
|
Definition
| specify what an object can do |
|
|
Term
|
Definition
| nothing more than an action that an object can perform |
|
|
Term
|
Definition
| information sent to objects to trigger methods, a function or procedure call from one object to another object. |
|
|
Term
|
Definition
| is hiding the implementation details by providing a layer over the basic functionality. |
|
|
Term
|
Definition
| is hiding the data which is being affected by that implementation. Use of private and public comes under this. For example, hiding the variables of the classes. |
|
|
Term
|
Definition
| is just grouping all similar data and functions into a group e.g Class in programming; Packet in networking. |
|
|
Term
|
Definition
| refers to a programming language's ability to process objects differently depending on their data type or class. More specifically, it is the ability to redefine methods for derived classes. |
|
|
Term
|
Definition
|
|
Term
| What is the primary difference between the traditional (structured) approach and the object-oriented approach? |
|
Definition
i. With Traditional approaches – problem decomposition is EITHER Process-centric or Data-centric.
ii. With Object-Oriented Methodologies – attempt to balance the emphasis between process and data by focusing on the decomposition of problems on objects that contain both data and processes.
1. Work on one business process and work down (NOT REALLY DECOMPOSITION WITH |
|
|
Term
| Object-Oriented Methodologies |
|
Definition
| attempt to balance the emphasis between process and data by focusing on the decomposition of problems on objects that contain both data and processes. |
|
|
Term
|
Definition
| problem decomposition is EITHER Process-centric or Data-centric. |
|
|
Term
|
Definition
| When we do traditional SDLC we create a dataflow diagram, we drill down to see which level is composed of, until we have reached the core. Start at the top and delve down into different areas of the business to learn more about them. |
|
|
Term
|
Definition
| describes how the user interacts with the system to perform some activity and models one business process |
|
|
Term
|
Definition
| means that use cases are used to describe a business processes. |
|
|
Term
| How many business processes does each use-case model |
|
Definition
| A Use case models exactly one business process. |
|
|
Term
| Rational Unified Process: |
|
Definition
| is a specific methodology that maps out when and how to use the various UNIFIED MODELING LANGUAGE (UML) techniques for object-oriented analysis and design. |
|
|
Term
|
Definition
| is use-case driven, architecture-centric, and iterative and incremental. |
|
|
Term
| Rup is a 2d system that includes |
|
Definition
|
|
Term
|
Definition
| 1) INCEPTION, 2) ELABORATION, 3) CONSTRUCTION, and 4) TRANSITION. |
|
|
Term
|
Definition
| 1) BUSINESS MODELING, 2) REQUIREMENTS, 3) ANALYSIS, 4) DESIGN, 5) IMPLEMENTATION, 6) TEST, 7) DEPLOYMENT, 8) CONFIGURATION and 9) CHANGE MANAGEMENT. |
|
|
Term
| What is important in all the workflows and some of the phases of RUP? |
|
Definition
| To keep the Primary deliverable in mind |
|
|
Term
|
Definition
| is similar to the planning phase (SDLC) where a business case is made for the proposed system, including a feasibility analysis. |
|
|
Term
| What are the 3 questions in Feasibility Analysis? |
|
Definition
1) “DO WE HAVE THE TECHNICAL CAPABILITY TO BUILD IT?” (technical feasibility)
2) “IF WE BUILD IT, WILL IT PROVIDE BUSINESS VALUE?”
3) “IF WE BUILD IT, WILL IT BE USED BY THE ORGANIZATION?” |
|
|
Term
| Primary Workflows in Inception Stage? |
|
Definition
| Business modeling, Requirements, and Analysis |
|
|
Term
| What is the Primary Deliverable of the Inception Phase |
|
Definition
1) SETS THE SCOPE of the project,
2) identifies the PRIMARY REQUIREMENTS and CONSTRAINTS,
3) SETS up an INITIAL PROJECT PLAN,
4) describes the FEASIBILITY and RISKS associated with the project, 5) ADOPTION of the NECESSARY ENVIRONMENT to develop the system, and
6) aspects of the PROBLEM DOMAIN CLASSES being implemented and tested. |
|
|
Term
| What does a vision document consist of? |
|
Definition
1) Introduction – purpose, scope, … overview
2) Positioning – business case, problem statement, product positioning statement
3) Stakeholder and User Descriptions – market demographics, stakeholders and users and their needs.
4) Product Overview – product perspective, summary of capabilities, assumptions and dependencies on other systems, cost and pricing, licensing and installation
5) Product Features – the functional requirements
6) Constraints
7) Quality Ranges
8) Precedence and Priority
9) Other Product Requirements - the non-functional requirements
10) Documentation Requirements
11) Feature Attributes – risk, stability, target release date, assigned to, reason. |
|
|
Term
|
Definition
| Deals with developing the vision document, including: 1) finalizing the business case, 2) revising the risk assessment, and 3) completing a project plan in sufficient detail for stakeholders to be able to agree with constructing the actual final system |
|
|
Term
| What are the Primary deliverables of the Elaboration Phase |
|
Definition
1) The UML structure and behavior diagrams
2) An executable of a BASELINE version of the evolving information system – SERVES as a FOUNDATION for ALL LATER ITERATIONS. |
|
|
Term
| What are the Workflows involved with the Elaboration Phase |
|
Definition
Developers are involved in all but the deployment engineering workflow.
As developers iterate over the workflows, addressing configuration and change management becomes apparent. |
|
|
Term
| Construction phase defined |
|
Definition
focuses heavily on programming the evolving system.
Primary deliverable of Construction phase is the implementation of the system that can be released for beta and acceptance testing. |
|
|
Term
| primary workflows during Construction phase |
|
Definition
The Implementation Workflow, however the requirements workflow and the analysis and design workflows also are involved.
• The configuration and change management workflow – with its version control activities becomes very important during the Construction phase. WITHOUT GOOD VERSION CONTROLS – rolling back to a previous version (incremental implementation) of the system is nearly impossible. |
|
|
Term
| When do you identify missing workflows |
|
Definition
| DURING THE CONSTRUCTION PHASE, helps to finish the analysis and design models they are finally completed |
|
|
Term
| Transition phase defined: |
|
Definition
– is associated with the implementation phase of the traditional SDLC approach.
Primary deliverable of the _______ phase is the actual executable information system;, user manuals, a plan to support the users, and a plan for upgrading the information system in the future. |
|
|
Term
|
Definition
| will have been executing during the earlier phases of the evolving system. Depending on the results from the testing workflow, some redesign and programming activities on the design and implementation workflows could be necessary. |
|
|
Term
| during Transition phase managers focus on |
|
Definition
| project management, configuration and change management and environment workflows. |
|
|
Term
| engineering workflows of the Unified Process |
|
Definition
| 1) business-modeling, 2) requirements, 3) analysis, 4) design, 5) implementation, 6) test, and 7) deployment workflows. |
|
|
Term
| Business-modeling workflow uncovers ? |
|
Definition
| problems and identifies potential projects within a user organization. |
|
|
Term
| Primary process of Business Modeling ? |
|
Definition
| is to ensure that both developer and user organizations understand where and how the to-be-developed information system fits into the business process of the user organization |
|
|
Term
| Requirements workflow includes: |
|
Definition
| eliciting both functional and nonfunctional requirements and are gathered from project stakeholders, including end users, managers within the end user organization and even customers. |
|
|
Term
| Analysis workflow addresses |
|
Definition
| the creation of an analysis model of the problem domain. |
|
|
Term
| Analysis workflow has __ steps |
|
Definition
i. Analyst designs the architecture associated with the problem domain by creating structural and behavioral diagrams that depict a description of the problem domain classes and their interactions.
ii. Primary Purpose of the analysis workflow – to ensure that both developer and user organizations understand the underlying problem and its domain without overanalyzing.
iii. ANALYSIS PARALYSIS!! – occurs when the system becomes so bogged down with analysis that the system is never actually designed or implemented.
iv. Emphasis on reusability – Identify useful reusable classes for class library. |
|
|
Term
| Design workflow transitions |
|
Definition
| the analysis model into a form that can be used to implement the system: The design model. Focuses on developing a solution that will execute in a specific environment. |
|
|
Term
|
Definition
the description of the evolving information system by adding classes that address the environment of the information system to the evolving analysis model.
1. Concerns…Class Design, optimization of the evolving information system, database design, user-interface design, and physical architecture design. |
|
|
Term
| Implementation workflow creates: |
|
Definition
| create an executable solution based on the design model (i.e. programming). |
|
|
Term
| Testing workflow increases |
|
Definition
the quality of the evolving system
i. Goes beyond the simple unit testing associated with the implementation workflow. Includes, testing the integration of all modules used to implement the system, user acceptance testing, and the actual alpha testing of the software. |
|
|
Term
| Deployment workflow is associated with |
|
Definition
the transition phase of the Unified process. Includes, activities such as software packaging, distribution, installation, and beta testing.
i. Used to produce the system to create software artifact – something used by a population. The software artifact is a part of the system |
|
|
Term
| supporting workflows of the Unified Process? |
|
Definition
| 1) project management, 2) configuration and change management, and 3) environment workflows. |
|
|
Term
| Project Management workflow include: |
|
Definition
| 1. Risk identification, Managements, scope management, estimating the time to complete each iteration and the entire project, estimating the cost of the individual iteration and the whole project ad tracking progress toward the evolving information system |
|
|
Term
| Configuration and Change Management Workflow include: |
|
Definition
1. The evolving information system comprises a set of artifacts, including diagrams, source code and executables.
a. Artifacts must have access controls to safeguard them from being stolen or destroyed.
b. Version control is used to manage continuous change to artifacts.
c. Project Management information needs to be captured. |
|
|
Term
|
Definition
| involves acquiring and installing all of the different tools to support the development of an object-oriented information system: programming environments (IDEs), project management tools and configuration management tools. |
|
|
Term
| Define project management |
|
Definition
| a. The process of planning and controlling the development of a system within a specified time frame at a minimum cost with the right functionality. |
|
|
Term
| Definition of Failure as it relates to PM |
|
Definition
| Functionality doesn’t work, or doesn’t work right, if the project is not on time or is delayed by a significant amount (defined by the project itself), if the project comes in significantly over budget/ over cost |
|
|
Term
| What is a system request and what should it contain? |
|
Definition
a document that describes the business reasons for building a system and the value that the system is expected to provide.
It should have 5 elements: Project Sponsor, Business Need, Business Requirements, Business Value, Special Issues and Constraints |
|
|
Term
|
Definition
| the person who initiates the project and who serves as the primary point of contact on the business side. |
|
|
Term
|
Definition
| The business-related reason for initiating the system. |
|
|
Term
|
Definition
| The business capabilities that the system will provide. |
|
|
Term
|
Definition
| the benefits that the system will create for the organization. |
|
|
Term
| Special Issues and Constraints |
|
Definition
| Issues that are relevant to the implementation of the system and decisions made by the committee about the project. |
|
|
Term
| How are new systems identified? |
|
Definition
| A project is ________ when someone in the organization identifies a business need to build a system. This could occur within a business unit or IT, come from a steering committee charged with identifying business opportunities, or evolve from a recommendation made by external consultants. |
|
|
Term
| How do we define business value? |
|
Definition
| Value is gained from the system through tangible and intangible value |
|
|
Term
|
Definition
| Can be quantified and measured easily |
|
|
Term
|
Definition
| results from an intuitive belief that the system provides important, but hard-to-measure, benefits to the organization |
|
|
Term
| What are the three types of feasibility that we studied |
|
Definition
| Technical, Economic, Organizational |
|
|
Term
|
Definition
the extent to which the system can be successfully designed, developed, and installed by the IT group.
a. Answers the question, “Can we build it?”
b. Are the analysts familiar with the technology. |
|
|
Term
|
Definition
identifies the financial risk associated with the project.
a. Answers the question, “Should we build the system?”
b. Identifying costs and benefits associated with the system, assigning values to them, and then calculating the cash flow and return on investment for the project. |
|
|
Term
| Organizational feasibility |
|
Definition
how well the system will be accepted by the users and incorporated into the ongoing operations of the organization.
a. Answers the question, “If we build it, will they come?”
b. Perform a Stakeholder analysis – a stakeholder is a person, group, or organization that can affect (or will be affected by) a new system). |
|
|
Term
| who is the Project Champion |
|
Definition
| someone who promotes the project. |
|
|
Term
| What are the different methods of calculating economic feasibility |
|
Definition
1. Identifying Costs and Benefits
2. Assigning Values to Costs and Benefits
3. Determining Cash Flow
4. Determining Net Present Value (NPV)
5. Determining Return on Investment (ROI)
6. Determining the Break-Even Point
7. Graphing the Break-Even Point. |
|
|
Term
| How are projects selected from among all project requests? |
|
Definition
| Projects provide value added vs risks. |
|
|
Term
| Portfolio Management defined |
|
Definition
| Before approving a project, the approval committee considers the project from an organizational perspective. The approval committee takes into consideration the different kinds of projects that exist in an organization –large and small, high risk and low risk, strategic and tactical. |
|
|
Term
| Project Portfolio defined |
|
Definition
1. A good project portfolio has the most appropriate mix of projects for the organization’s needs.
2. Projects are prioritized within the project portfolio. |
|
|
Term
|
Definition
| a list of tasks where each step is broken down in turn and numbered hierarchically. |
|
|
Term
|
Definition
| A horizontal bar chart that shows the same task information as the project Work Breakdown structure, but in a graphical way. |
|
|
Term
|
Definition
| Used to find the critical path of the project |
|
|
Term
|
Definition
| unit of work that will be performed by a member or members of the development team. |
|
|
Term
|
Definition
important dates, identified on the workplan.
1. After a milestone, some reporting is required, what was done, were all the tasks complete, home much did they cost, how much time did it take? |
|
|
Term
|
Definition
Program Evaluation and Review Technique – a network analysis technique that can be used when the individual task time estimates are fairly uncertain.
a. Uses three time estimates: optimistic, most likely, and a pessimistic and combines the three into a single weighted average estimate. |
|
|
Term
|
Definition
| 1. Critical Path Method – allows the identification of the critical path in the network. The critical path is the longest path from the project inception to completion. |
|
|
Term
| Project Estimation defined |
|
Definition
| making trade-offs among three important concepts: the functionality of the system, the time to complete the project and the cost of the project.b. Estimation time process: is the process of assigning project values for time and effort. |
|
|
Term
|
Definition
a. A dynamic schedule that records and keeps track of all the tasks that need to be accomplished over the course of the project.
1. Iterative and incremental for the rational unified process. |
|
|
Term
|
Definition
| Total time to complete a project. |
|
|
Term
|
Definition
Any of the functionality that is required within the project.
1. Sometimes you define functionality that is not in the scope |
|
|
Term
|
Definition
| Expanding the scope of the project, causes time and budget to go up |
|
|
Term
|
Definition
a. You have a deadline, you have to work backwards.
1. Set the date for system delivery
2. Prioritize the functionality that needs to be included in the system.
3. Build the core of the system (the functionality ranked as most important).
4. Postpone functionality that cannot be provide within the time frame.
5. Deliver the system with core functionality
6. Repeat steps 3 through 5 to add refinements and enhancements. |
|
|
Term
| During Time Boxing process |
|
Definition
| quality isn’t reduced, just is prioritized. |
|
|
Term
| Name 3 ways in which project delay can be handled. |
|
Definition
a. If you assume the rest of the project is simpler than the part that was late and is also simpler than believed when the original schedule estimate were made, you can make up lost change – DO NOT CHANGE SCHEDULE.
b. If you assume the rest of the project is simplier than the part that was late and is no more complex than the original estimate assumed, you can’t make up the lost time, but you will not lose time on the rest of the project – INCREASE THE ENTIRE SCHEDULE BY THE TOTAL AMOUNT OF TIME THAT YOU ARE BEHIND.
c. If you assume that the rest of the project is as complex as the part that was late, then all the scheduled dates in the future underestimate the real time required by the same percentage as the part that was late – Increase the entire schedule by the percentage of weeks that you are behind. |
|
|
Term
| List several causes of risk |
|
Definition
a. Weak Personnel, Scope Creep, Poor Design, and Overly Optimistic Estimates.
b. Scope Creep is the single greatest reason for Project delay |
|
|
Term
|
Definition
| is a single repository for user requirements.. • The biggest single thing that it can be used for is to trace requirements through the development process. Traceability. |
|
|
Term
| Rational Software Architect |
|
Definition
Modelling,
• Functional modeling: Use-cases, Structural Modelling, Class Diagrams, Behavioral Diagrams. |
|
|
Term
| What is the purpose of requirements determination |
|
Definition
| To turn the very high-level explanation of the business requirements stated in the system request into a more precise list of requirements that can be used as inputs to the rest of analysis (creating functional, structural, and behavioral models). |
|
|
Term
| What is the difference between a functional and a non-functional requirement? Give an example of each. |
|
Definition
Functional requirements: relates directly to a process a system has to perform or information it needs to contain,
…such as requirements that state that a system must have the ability to search for available inventory or to report actual and budgeted expenses are functional requirements.
b. Non Functional requirements: refer to behavioral properties that the system must have,
… such as: Performance, Usability and Security. |
|
|
Term
| What is the purpose of defining the system requirements? |
|
Definition
| The purpose of _______ definition is to provide the information needed by the other deliverables in analysis. Which include functional, structural, models and to define the scope of the project. |
|
|
Term
| List several ways in which an analyst can determine system requirements. |
|
Definition
Interviews
Joint Application Design – an information-gathering technique that allows the project team, users, and management to work together to identify requirements for the system.
Questionnaires – target a large number of users
Document Analysis
Observation |
|
|
Term
| Be familiar with how the various requirements gathering techniques differ |
|
Definition
Type of information As-is, improvements to-be As-is, improvements to be. As-is improvements As-is As-is
Depth of information High High Medium Low Low
Breadth of information Low Medium High High Low
Integration of information Low High Low Low Low
User involvement Medium High Low Low Low
Cost Medium Low-Medium Low Low Low to Medium |
|
|
Term
| What are the three requirements analysis strategies? |
|
Definition
| Business Process automation (BPA), business process improvement (BPI), and business process reengineering (BPR). BPA creates a small amount of change, BPI creates a moderate amount of change and BPR creates significant change that affect much of the organization. |
|
|
Term
| Business Process automation (BPA), |
|
Definition
| creates a small amount of change |
|
|
Term
| business process improvement (BPI) |
|
Definition
| creates a moderate amount of change |
|
|
Term
| business process reengineering (BPR) |
|
Definition
| creates significant change that affect much of the organization. |
|
|
Term
| Which of these requires the most change |
|
Definition
| Business Process Reengineering (BPR) |
|
|
Term
|
Definition
| asks the users and managers to identify problems with the as-is system and to describe how to solve them in the to-be system. |
|
|
Term
|
Definition
| 2. The ideas produced by problem analysis tend to be solutions to problems, but sometimes the solutions only address a symptom of the problem, not the true problem or root cause, which focuses on problems not solutions. |
|
|
Term
|
Definition
| requires a detailed examination of the amount of time it takes to perform each process in the current as-is system. |
|
|
Term
|
Definition
| is a similar analysis; it examines the cost of each major process or step in a business process rather than the time taken. |
|
|
Term
|
Definition
| the managers and analysts think about other organizations or visit them as customers to watch how the business process is performed, in order to learn how your organization can do something better |
|
|
Term
|
Definition
| focuses on understanding the fundamental outcomes that provide value to customers |
|
|
Term
|
Definition
| starts by having the analysts and managers develop a list of important and interesting technologies. Then, the group systematically identifies how every technology could be applied to the business process and identifies how the business would benefit |
|
|
Term
|
Definition
| the analysts and managers work together to identify how the organization could eliminate each activity in the business process, how the function could operate without it, and what effects are likely to occur. |
|
|
Term
| Describe the interview process. Include the chronological steps that you should follow. |
|
Definition
a. Interview process is the most commonly used requirements-gathering technique. Interview people at different levels of the organization to get different perspectives.
1. Select Interviewees
2. Design Interview Questions
3. Prepare the interview
4. Conduct the interview
5. Post-Interview Follow-up |
|
|
Term
| List 3 types of interview questions and give an example of each |
|
Definition
| Closeded ended, Open-ended, and Probing questions |
|
|
Term
|
Definition
| require a specific answer (e.g. how many credit card requests are received per day). |
|
|
Term
|
Definition
| allow for room for elaboration on the part of the interviewee. Used to gather rich information (e.g. What is the most difficult problem when using the As-Is system?) |
|
|
Term
|
Definition
| follow up on what has just been discussed in order to learn more, when the interviewer is unclear about answer form the interviewee. (I.E. So you mentioned this part of system is difficult to work with, could you elaborate on what particular part of the system makes it difficult to work with?) |
|
|
Term
| Why is an interview follow-up important? |
|
Definition
a. After the initial interview, the Analyst NEEDS to prepare an interview report that describes the information from the interview within 48 hrs after the interview. The report contains interview notes information that was collected over the course of the interview.
1. Often, after the interview report is sent to the interviewee with a request to read it and inform the analyst of clarifications or updates.
a. The user may mean different things than what the analyst understood. You may need to schedule a second interview |
|
|
