Term
|
Definition
| A group of programming-centric methodologies which focus on streamlining the SDLC |
|
|
Term
|
Definition
| Stores diagrams and other project information such as screen and report designs, and it keeps track of how the diagrams fit together |
|
|
Term
| Computer Aided Software Engineering |
|
Definition
| Is a category of software that automates all or part of the development process. Some software packages are primarily used during the analysis phase to create integrated diagrams of the systems and to store information regarding the system componenets (Often known as Upper Case). Others are design-phase tools that create the diagrams and then generate the code for data base tables and system functionality (often known as Lower Case) |
|
|
Term
|
Definition
| When features suggested by users are not well understood or there are challenging technical issues to be solved, each issue is examined by analyzing, designing and building a design prototype. A design prototype is NOT intended to be a working system, but only contains enough details to enable users to understand the issues under construction |
|
|
Term
|
Definition
| Includes detailed information about the SDLC...helps others when building or understanding what the system is designed to do |
|
|
Term
|
Definition
| Usually assigned to manage a group of analysts |
|
|
Term
|
Definition
| Contains tools used in both upper CASE and lower CASE tools |
|
|
Term
|
Definition
| Breaks a system into a series of sequentially developed versions. The first version contains the main requirements while the next versions have more features based on user feedback. |
|
|
Term
|
Definition
| Design phase tool that create the diagram s then generates the code for database tables and system functionality |
|
|
Term
|
Definition
| A formalized approach to implementing SDLC |
|
|
Term
|
Definition
| Since waterfall development takes so long, Parallel development was designed to speed up the process. Overall a general design for the whole system is performed and then the project is divided into a series of sub projects which are integrated at the end. |
|
|
Term
| Project Portfolio Management |
|
Definition
| A process of selecting , prioritizing, and monitoring project results |
|
|
Term
| Rapid Application Development (RAD) |
|
Definition
| Collection of methodologies created in response to weakness and slowness in Waterfall methodology. |
|
|
Term
|
Definition
| A document that tracks potential risks along with a evaluation of the likelihood of the risk and its potential impact on the project |
|
|
Term
|
Definition
| The process of assessing and addressing the risks that are associated with developing a project. Risks; weak personal, scope creep, poor design, overly optimistic estimated |
|
|
Term
|
Definition
| Oversees the progress of a group of programmers and more technical staff members |
|
|
Term
|
Definition
| Spends more time in the planning phase, uses prototypes of the system to explore design alternatives rather than as the actual system |
|
|
Term
|
Definition
| Used in a project that is schedule driven. Used mainly in RAD methadology...this technique sets a fixed deadline for a project and delivers the system by that deadline no matter what, even if functionality must be reduced |
|
|
Term
|
Definition
| Software package primarily used in the analysis phase to create integrated diagrams of the system and to store information regarding the system components. |
|
|
Term
|
Definition
| A Variation of Waterfall Development which pays more attention to testing* A key concept of this model is that as requirements are specified and components designed, testing for those elements are also designed. |
|
|
Term
|
Definition
| USed in iterative development, when the project is broken down into a series of versions that are developed sequentially |
|
|
Term
|
Definition
| A top down approach whereby high level tasks are defined then broken down into subtasks |
|
|
Term
|
Definition
| The mechanism used to manage the tasks that are listed in the WBS...The Work Plan is the Project Manager's primary tool for managing the project |
|
|
Term
|
Definition
| The process in which users and analysts proceed sequentially from one stage of the project to the next |
|
|
Term
|
Definition
| A list of project ground rules, and a list of expected norms for the team (when they should be at work, when staff meetings will be held, how will they communicate) |
|
|
Term
|
Definition
| Three Steps 1) Understand the existing situation, 2) Identify improvements, and 3) Define Requirements for the new system |
|
|
Term
|
Definition
| Analysis strategy is developed to guide the project team's efforts. Usually includes a study of the current system and its problems and envisioning ways to design a new system |
|
|
Term
|
Definition
| Helps to identify the business value that the proposed system will create. Also helps to develop ideas for improving the business process, and design new business processes and policies. |
|
|
Term
|
Definition
| Defines if the system will be developed by the company's own programmers, whether its development will be outsourced to another firm, or whether the company will buy an existing software package |
|
|
Term
|
Definition
| Focuses on the Tech issues surrounding the ways the system will interact with the organizations technical infastructure |
|
|
Term
| Organizational Feasibility |
|
Definition
| How the new system will be accepted by the users and how will it integrate with the current system. |
|
|
Term
| Organizational Management |
|
Definition
| Know about the project/budget enough money for the project/ Encourage users to accept and use the system. They also make presentations to management abou the objectives of the project and the proposed benefits. Market the benefits of the new system...basically they need to market the project to management.. |
|
|
