What is Artifacts ? How its Start in Inception ?

What Is Artifacts ? 

In the context of software development, artifacts refer to any document or deliverable produced as part of the software development process. These artifacts can take many forms, including diagrams, models, specifications, plans, and reports, among others. The purpose of artifacts is to capture and communicate information about the software being developed, its requirements, design, and implementation, as well as to support collaboration and decision-making among stakeholders.

The inception phase of software development is the first phase in many software development methodologies, including the Rational Unified Process (RUP), the Unified Process (UP), and the Agile development methodologies, such as Scrum and Extreme Programming (XP). The goal of the inception phase is to establish a shared understanding of the project's goals, scope, and constraints, as well as to define a high-level vision of the software being developed. The inception phase is typically characterized by a number of activities, including requirements gathering and analysis, stakeholder identification and communication, and architecture and design.

The artifacts created in the inception phase will depend on the specific development methodology being used, as well as on the needs and characteristics of the project. In general, however, the artifacts created in the inception phase are intended to capture and communicate information about the project's goals, requirements, scope, risks, and stakeholders.

Artifacts Created In Inception Phase 

Some of the most common artifacts created in the inception phase are described below.

1. Vision document

The vision document is a high-level document that describes the overall goals and objectives of the project, as well as the context in which the software is being developed. The vision document typically includes a description of the problem that the software is intended to solve, the benefits that the software will provide, and the stakeholders who will be impacted by the software. The vision document may also include a description of the constraints and risks associated with the project, as well as a high-level plan for how the project will be executed.

2. Use case model

The use case model is a graphical model that describes the functional requirements of the software being developed. The use case model typically includes a set of use cases, which describe the interactions between the software and its users, as well as any other actors that may interact with the software. Each use case describes a specific scenario in which the user interacts with the software, and includes a set of steps or actions that the user must perform to achieve their goals.

3. Supplementary specification

The supplementary specification is a document that describes the non-functional requirements of the software being developed. Non-functional requirements include factors such as performance, scalability, reliability, usability, and security. The supplementary specification typically includes a description of each non-functional requirement, as well as any constraints or guidelines that must be followed to ensure that the requirement is met.

4. Business model

The business model is a graphical model that describes the business context in which the software is being developed. The business model typically includes a description of the organization or enterprise that is developing the software, as well as a description of the processes and workflows that the software is intended to support. The business model may also include information about the stakeholders who will be impacted by the software, as well as any regulatory or compliance requirements that must be followed.

5. Initial project plan

The initial project plan is a document that describes the high-level plan for how the project will be executed. The initial project plan typically includes information about the project schedule, budget, resources, and milestones. The initial project plan may also include a description of the development methodology being used, as well as any risks or challenges that must be addressed during the project.

6. Risk list

The risk list is a document that identifies and prioritizes the risks associated with the project. Risks may include technical risks, such as the risk of a key technology not working as expected, as well as business risks, such as the risk of a change in market conditions impacting the project's success. The risk list typically includes a description of each risk, as well as an assessment of the likelihood and impact of the risk occurring. The risk list may also include a description of any mitigation strategies that can be put in place to reduce the likelihood or impact of the risk.

7. Prototype

A prototype is a working model of the software being developed that is used to validate and refine the requirements and design of the software. A prototype may be created using different levels of fidelity, from a low-fidelity prototype that only demonstrates the basic functionality of the software, to a high-fidelity prototype that closely resembles the final product. Prototypes can be used to obtain feedback from stakeholders, validate the feasibility of the software solution, and refine the requirements and design of the software.

Conclusion

In conclusion, the inception phase of software development is a critical phase that sets the foundation for the rest of the software development process. The artifacts created in the inception phase help to establish a shared understanding of the project's goals, scope, and constraints, as well as to define a high-level vision of the software being developed. By creating these artifacts, stakeholders can collaborate more effectively and make informed decisions about the software being developed.