CODE RELATED
ARTIFACTS
What is an Artifacts? (Software Development)
- An artifact is one of many kinds of tangible
by-products produced during the development
development of software. Some artifacts help
help describe the function, architecture, and
and design of software. Other artifacts are
concerned with the process of development
itself—such as project plans, business cases,
and risk assessments.
TYPES OF SOFTWARE ARTIFACTS
1. Project Management
-Project management focuses on planning
and organizing a project and its resources.
This includes identifying and managing the
lifecycle to be used, applying it to the user-
user-centered design process, formulating the
the project team, and efficiently guiding the
the team through all phases until project
EXAMPLE
-Class Diagrams
Class diagrams are the blueprints of your system
system or subsystem. You can use class diagrams
diagrams to model the objects that make up the
the system, to display the relationships between
between the objects, and to describe what those
those objects do and the services that they
provide. Class diagrams are useful in many
stages of system design.
-Walkthroughs
Walkthroughs are step-by-step
software solutions that guide users
through a series of actions to help
them complete a process. They are
used to train people on specific
workflows, tasks, new software, and
apps.
- End-User Documentation
User documentation is a type of technical
documentation content created to help
end-users understand how to use a
product and troubleshoot common issues.
End-users refer to customers or users of a
product, ie. Those who are setting up and
using a product on a regular basis.
- Internal Documentation
Internal documentation is the practice of
authoring and maintaining clearly detailed
processes and procedures for reference by your
internal team members.
- Criteria
With these artifacts, the client or the project
manager lays out the requirements of the
software or project to give developers a specific
- Unified Modeling Language (UML)
UML is used to visualize and plot out the
software and how it works including links
and processes.
- Risk Assessments
These describe all potential risks and
pitfalls when it comes to the software, so
developers can find ways to avoid and
2. Code Artifacts
- Created by developers and site
reliability engineers, code artifacts let
them test their work in detail before the
the software is launched. This is the
best way to avoid glitches later on.
- Test Suits
Test suites are the logical grouping or collection of
of test cases to run a single job with different test
test scenarios.
- Setup Scripts
A setup script is a collection of event handlers,
functions called by those event handlers, and data
used by the event handlers and functions.
- Compiled code
A compiled language is a programming language
where the source code is translated into machine
machine code and the machine code is stored in
a separate file.
- Test output
These artifacts are connected to the test suites
as they include the logs and results from the
testing phase.
- Microservises
Microservices are an architectural and
organizational approach to software
development where software is composed
composed of small independent services
that communicate over well-defined APIs.
APIs. These services are owned by small,
self-contained teams.
DOCUMENTATION ARTIFACTS
A Document Artifact is like a word processor
processor file that can be created and
stored directly inside the model to record
structured documentation. It is a light-
weight and convenient alternative to
creating a document in your favorite word
processor.
- End-user agreement
End-user agreement Is a legal contract between a software
software supplier and a customer or end-user, generally
made available to the customer via a retailer acting as an
an intermediary.
- Internal document
An internal document is a record that is created and stored
within a business. The document is used to support the
processes of the organization. Examples of internal
documents are employee timecards and timesheets,
production plans, purchase requisitions, receiving reports,
sales orders, and scrap authorizations.

CODE-RELATED-ARTIFACTS-CPAR.powerpoint.arts

  • 1.
  • 2.
    What is anArtifacts? (Software Development) - An artifact is one of many kinds of tangible by-products produced during the development development of software. Some artifacts help help describe the function, architecture, and and design of software. Other artifacts are concerned with the process of development itself—such as project plans, business cases, and risk assessments.
  • 3.
    TYPES OF SOFTWAREARTIFACTS 1. Project Management -Project management focuses on planning and organizing a project and its resources. This includes identifying and managing the lifecycle to be used, applying it to the user- user-centered design process, formulating the the project team, and efficiently guiding the the team through all phases until project
  • 4.
    EXAMPLE -Class Diagrams Class diagramsare the blueprints of your system system or subsystem. You can use class diagrams diagrams to model the objects that make up the the system, to display the relationships between between the objects, and to describe what those those objects do and the services that they provide. Class diagrams are useful in many stages of system design.
  • 5.
    -Walkthroughs Walkthroughs are step-by-step softwaresolutions that guide users through a series of actions to help them complete a process. They are used to train people on specific workflows, tasks, new software, and apps.
  • 6.
    - End-User Documentation Userdocumentation is a type of technical documentation content created to help end-users understand how to use a product and troubleshoot common issues. End-users refer to customers or users of a product, ie. Those who are setting up and using a product on a regular basis.
  • 7.
    - Internal Documentation Internaldocumentation is the practice of authoring and maintaining clearly detailed processes and procedures for reference by your internal team members. - Criteria With these artifacts, the client or the project manager lays out the requirements of the software or project to give developers a specific
  • 8.
    - Unified ModelingLanguage (UML) UML is used to visualize and plot out the software and how it works including links and processes. - Risk Assessments These describe all potential risks and pitfalls when it comes to the software, so developers can find ways to avoid and
  • 9.
    2. Code Artifacts -Created by developers and site reliability engineers, code artifacts let them test their work in detail before the the software is launched. This is the best way to avoid glitches later on.
  • 10.
    - Test Suits Testsuites are the logical grouping or collection of of test cases to run a single job with different test test scenarios. - Setup Scripts A setup script is a collection of event handlers, functions called by those event handlers, and data used by the event handlers and functions.
  • 11.
    - Compiled code Acompiled language is a programming language where the source code is translated into machine machine code and the machine code is stored in a separate file. - Test output These artifacts are connected to the test suites as they include the logs and results from the testing phase.
  • 12.
    - Microservises Microservices arean architectural and organizational approach to software development where software is composed composed of small independent services that communicate over well-defined APIs. APIs. These services are owned by small, self-contained teams.
  • 13.
    DOCUMENTATION ARTIFACTS A DocumentArtifact is like a word processor processor file that can be created and stored directly inside the model to record structured documentation. It is a light- weight and convenient alternative to creating a document in your favorite word processor.
  • 14.
    - End-user agreement End-useragreement Is a legal contract between a software software supplier and a customer or end-user, generally made available to the customer via a retailer acting as an an intermediary. - Internal document An internal document is a record that is created and stored within a business. The document is used to support the processes of the organization. Examples of internal documents are employee timecards and timesheets, production plans, purchase requisitions, receiving reports, sales orders, and scrap authorizations.