Management Artifacts includes overseeing whole condition or situation to confirm and ensure that instructional technology project gets done. It contains various activities that capture intermediate results and supporting information and data that are essential to document the end-product/process legacy, maintain the end-product, increase quality of product, and also increases performance of the process.
Some types of Management Artifacts :
- Business Case –
The business case generally provides justification for initiating project, task, program, or portfolio. This justification is simply based on the estimated cost of the development and implementation against risks and issues and evaluated business benefits and savings to be gained.
It is created and developed during early stages of project and simply explains why, what, how, and who necessary to decide whether if it is worthwhile continuing or initiating project. A business case is good if describes problems and issues, determines all the possible options to address it, and gives permission to the decision-makers to decide which of the course of the action will be best for organization. The main goal of business case to convert vision into economic teams so that organization can develop exact and accurate ROI (Return on Investment) assessment.
- Software Development Plan (SDP) –
Software development plan aims to lay out whole plan which is necessary and required in order to develop, modify, and upgrade software system. It is ready-made solution for managers for software development. It provides acquirer insight and tool for checking processes that have to be followed for development of software.
It simply indicates two things: Periodic updating and understanding and approval by managers and practitioners alike.
- Work Breakdown Structure (WBS) –
Work breakdown structure is deliverable-oriented breakdown of project into component of small size. WBS is created and developed to establish similar understanding of scope of project.
It is hierarchical tree structure that layout project and simply breaks it down into smaller and manageable portions or components. It is vehicle for budgeting and collecting or gathering costs.
- Software Change Order Database –
For Iterative development process, primary task to manage change. A project can iterate (perform repeatedly) more productively with large change freedom. This change of freedom has been gained due to automation.
- Release Specification –
Release specifications generally mean tests and limits against that which raw material, intermediate and end product are accurately measured just before use or release.
Two important forms of requirements in release specifications are Vision Statement (captures contract between development group and buyer) and Evaluation Criteria (management-oriented requirements that can be showed and represented using use cases, use cases realizations, etc).
- Deployment –
The deployment includes numerous subsets of documents for transitioning product into operational status. It is simply application code as it runs on production: built, bundled, compiled, etc. It is process of putting artifact where it is necessary and performing any tasks it needs so as to achieve its purpose. It can also include computer system operations manuals, software installations manuals, plans and procedures for cutover, etc.
- Environment –
Automation of development process needs and important to get supported by robust development environment. It must include following points :
- Management of requirements.
- Visual Modeling.
- Automation of document.
- Automated regression testing.
- Tools of host and target programming.
- Tracking of features and defects or errors.
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.
- Pragmatic Artifacts
- Engineering Artifacts
- Introduction of Test Artifacts
- Module Coupling and Its Types
- Traceability and its types
- Data Preprocessing and Its Types
- Principles of Risk Management and Paradigm
- Six Sigma and Lean Model of Project Management
- Tools and Techniques Used in Project Management
- Difference between Management Information System (MIS) and Computer Science (CS)
- Software Engineering | System configuration management
- Software Engineering | Software Project Management Complexities
- Software Engineering | Project Management Process
- Integrating Risk Management in SDLC | Set 1
- Integrating Risk Management in SDLC | Set 2
- Integrating Risk Management in SDLC | Set 3
- Software Engineering | Software Project Management (SPM)
- Software Engineering | Risk Management
- Software Engineering | Software Project Management Plan (SPMP)
- Basics of management
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to firstname.lastname@example.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.