Your SlideShare is downloading. ×
Artifacts
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Artifacts

585

Published on

Artifacts Of The Proces

Artifacts Of The Proces

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
585
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
28
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Artifacts OF THE PROCESS Presented By : o Nitin Nirmal 25 o Hitesh Shetty 44 o Mahesh Tawde 52 o Mayuresh Wadekar 64 1
  • 2. Artifact Sets Fig. Overview of Artifact Sets 2
  • 3. Engineering sets Requirement Set: This is primary engineering context for evaluating other three artifact sets. Design Set: The design set contains varying levels of abstraction that represent component of solution space Implementation Set: The implementation set includes source code that represents tangible information of components Deployment Set: Deployment set includes user deliverables and machine language notations ,executable software, build scripts and I installation scripts to use product in target environment. 3
  • 4. Lifecycle focus on artifact sets 4
  • 5. Artifact evolution over lifecycle 5
  • 6. Test ArtifactsTest artifacts Must be develop. concurrently with product. Implemented in programmable and repeatable formats. Documented the same way as products.It Would Contain Following Artifacts,  Management Set  Requirement Set  Design Set  Implementation Set  Deployment Set 6
  • 7. Management Artifacts Business Case : It provides all information necessary to determine whether the project is worth investing in. 7
  • 8. Management Artifacts Work Breakdown Structure: It is the vehicle for budgeting and collecting costs. It will result in functional breakdown of structure 8
  • 9. Management Artifacts Software change order database: They automate data entry and maintaining change records on-line. Release Specification: 9
  • 10. Management Artifacts Release Description: It describes the result of each release including performance against each of the evaluation criteria in corresponding release specification. 10
  • 11. Management Artifacts Status Assessment: It provides periodic snapshots of project health and status,including software project manager’s risk assessment, quality indicators,and management indicators. Environment: Important emphasis of a modern approach is to define thedevelopment and maintenance environment as a first class artifact of theprocess. Deployment: This includes several document subsets for transitioning theproduct into operational status 11
  • 12. Engineering Artifacts Vision Document: It provides a complete vision for the software under development and support the contract between the funding authority and development organization.  Software User Manual : It provides the user with reference documentation necessary to support the delivered software. 12
  • 13. Engineering Artifacts Architecture Description: It provides an organized view of software architecture under development 13
  • 14. Pragmatic ArtifactsThis philosophy raises the following cultural issues: People want to review information but dont understand the language of the artifact. People want to review the information but dont have access to the tools. Human-readable engineering artifacts should use rigorous notations that are complete, consistent, and used in a self-documenting manner. Useful documentation is self-defining: It is documentation that gets used. Paper is tangible; electronic artifacts are too easy to change. 14
  • 15. uThank You 15

×