all Artifacts compare

 In software development, "artifacts" refer to any tangible byproduct created during the project lifecycle. These are typically categorized based on their primary purpose and the audience they serve. Here's a tabular comparison of Engineering, Pragmatic, and Management artifacts:

FeatureEngineering ArtifactsPragmatic ArtifactsManagement Artifacts
Primary PurposeDefine, build, test, and deploy the software system.Support the practical execution and environment of the project.Plan, track, control, and oversee the project.
AudienceDevelopers, Architects, Testers, Technical Leads.Developers, Testers, System Administrators, Operations.Project Managers, Stakeholders, Customers, Sponsors.
NatureTechnical, often formal, detailed specifications.Practical, often configuration-related, environmental.Strategic, organizational, financial.
Examples- Requirements Specification (e.g., Use Cases, User Stories)<br>- Design Models (e.g., UML diagrams, Architecture Diagrams)<br>- Source Code<br>- Test Cases/Scripts<br>- Executable Binaries<br>- API Documentation- Development Environment Setup Scripts<br>- Build Scripts<br>- Deployment Scripts<br>- Configuration Files<br>- Test Data<br>- Toolchain specifications<br>- Standard Operating Procedures (SOPs)- Business Case<br>- Project Plan (Schedule, Budget, Resources)<br>- Risk Management Plan/Register<br>- Communication Plan<br>- Status Reports<br>- Stakeholder List<br>- Work Breakdown Structure (WBS)
EvolutionEvolve through refinement and implementation.Evolve with environment changes and automation needs.Evolve with project progress and changing objectives.
FocusHow the software works and is built.How the software is supported and deployed.Why the project is being done and if it's on track.
RelationshipDirectly create the product.Enable and facilitate the engineering and deployment.Govern the entire project, including engineering and pragmatic activities.

Comments

Post a Comment

Popular posts from this blog

ch 2 pm

 Here's a breakdown of the Software Engineering Institute's (SEI) Capability Maturity Model Integration (CMMI) framework elements, particularly relevant to the Unified Process (UP) and other structured methodologies: Framework Elements: Life Cycle Phases: Inception: Focuses on establishing the project's vision, scope, business case, and feasibility. Elaboration: Defines the architecture, refines requirements, and plans the remaining project. Mitigates high-risk elements. Construction: Iteratively develops and integrates the bulk of the software, building working versions. Transition: Deploys the software to the user community and ensures operational readiness. (Note: Your request mentioned "training phase" which often aligns with Transition activities.) Artifacts of the Process: The Artifact Sets (Categories): Management Artifacts: Pertain to project planning, tracking, and control (e.g., business case, project plan, risk list). Engineering Artifacts...
Read more

pm unit :1

Evolution of software economics. short and efficient: The evolution of software economics reflects a shift from a "craft" to a more industrialized, predictable process. Early Days (1960s-1970s - Conventional/Craftsmanship): Characteristics: Custom tools, custom processes, primarily custom components built in primitive languages. Economics: Highly unpredictable; cost, schedule, and quality objectives were frequently underachieved. Focus was on basic analysis and coding. Transition (1980s-1990s - Software Engineering): Characteristics: Emergence of repeatable processes and off-the-shelf tools. Higher-level languages became prevalent. Some commercial components (OS, databases, networking) were adopted. Economics: Still somewhat unpredictable, but improvements in process and tooling started to offer better control. Software cost models like COCOMO emerged to estimate effort based on factors like size, process, personnel, environment, and quality. Modern Practices (2000...
Read more

ch 3 pm

  Iterative Process Planning: Instead of a single, rigid plan, this involves continuous refinement of project plans in small cycles (iterations). Each iteration builds on the last, allowing for flexibility, early feedback, and adaptation to changing requirements and risks. This is a hallmark of Agile methodologies. Project Organizations and Responsibilities: Defines the roles, responsibilities, and reporting structures within a software development team (e.g., project manager, architects, developers, testers). It also addresses how teams are structured (e.g., functional, matrix, cross-functional) to maximize efficiency and communication. Process Automation: Leveraging tools and scripts to automate repetitive and error-prone tasks across the software development lifecycle. This includes automated builds, testing (Continuous Integration/Delivery - CI/CD), deployment, environment provisioning (Infrastructure as Code), and reporting, significantly boosting efficiency and quali...
Read more