View TRAK:PrVp-02 Procurement Timeline Viewpoint

TRAK_logo_60.jpg

Title

PrVp-02 - Procurement Timeline Viewpoint

Version

8

Date

8th December 2017

Overview

The PrVp-02 - Procurement Timeline Viewpoint is part of the TRAK Procurement Perspective and one of the 21 TRAK Architecture Viewpoints.

The PrVp-02 Procurement Timeline Viewpoint describes the dependencies between projects as a result of the introduction or removal of systems.

It is the specification for the TRAK::PrV-02 Procurement Timeline architecture view.

Stakeholders Addressed

  • Owner of Enterprise
  • Builder of Enterprise
  • User of Concept
  • Owner of Solution
  • Acquirer of Solution
  • Developer of Solution
  • Operator of Solution
  • Trainer of Solution
  • Maintainer of Solution
  • Disposer of Solution

Concerns Addressed

What other projects is this dependent on? How does their delivery time affect us?

Covered by TRAK IPR and licenses

Description

Describes the dependencies between projects as a result of the introduction or removal of systems.

Covered by TRAK IPR and licenses

Declared Tuples

  • Project owns Milestone
  • Project Activity marked by Milestone
  • Milestone marks introduction of  System
  • Milestone marks removal of System

OR

OR

Covered by TRAK IPR and licenses

Optional Tuples

Context - Project Structure:

Universal:

If any of these optional metamodel elements are added then the appropriate TRAK Master Architecture View must be provided.

Covered by TRAK IPR and licenses

Well-Formedness

A PrV-02 view shall contain:

  • at least 2 Systems OR at least 2 Project Activities (trying to show dependencies between project activities via the system(s)) (using ‘Project Activity delivers / removes System is necessary for Project Activity’)
  • each System and Project Activity must be connected to its Project (using ‘Project undertakes Project Activity delivers / removes System’ or ‘Project owns Milestone marks introduction of / marks removal of System’)
  • at least one System (the subject of the view - it shows the procurement / effect of time on the solution)
  • every Project Activity must have start and finish dates or a Concern attached flagging the absence i.e. Concern about Project Activity

Covered by TRAK IPR and licenses

Presentation

block diagram form:

PrVp-02_examplePresentation_block_430.gif

Full size:File:PrVp-02 examplePresentation block.gif

Note: Since start and finish dates are not shown/accessible only the dependency of Project Pro01-02 on Project Pro01-01 via System Sys35 is known.

Covered by TRAK IPR and licenses

Examples

Views Needed to Construct

See Minimum Allowed View Sets

Covered by TRAK IPR and licenses

Consistency Rules

The relationships between Milestone and System and Project Activity and System must be consistent:

  • IF {Project undertakes Project Activity delivers System THEN NOT {(same) Project owns Milestone marks removal of (same) System}
  • IF {Project undertakes Project Activity removes System} THEN NOT {(same) Project owns Milestone marks introduction of (same) System}
  • IF {Project owns Milestone marks removal of System} THEN NOT {(same) Project undertakes Project Activity delivers (same) System}
  • IF {Project owns Milestone marks introduction of System} THEN NOT {(same) Project undertakes Project Activity removes (same) System}

Further rules are applied through the TRAK Bye Laws

Covered by TRAK IPR and licenses

Configuration History

The TRAK Viewpoints project on Sourceforge (trakviewpoints.sourceforge.net) maintains a version-controlled repository. The change record is at http://trakviewpoints.svn.sourceforge.net/viewvc/trakviewpoints/trunk/?view=log

Comments

The PrV-02 is the master architecture view for Milestone, Project Activity.

Attributes/properties for Project Activity e.g. start and finish dates are specified in the TRAK Metamodel document.

Covered by TRAK IPR and licenses

It is important to note that architectural modelling is not a substitute for programme management nor UML modelling tools a substitute for project tools. TRAK makes no attempt to replicate either and instead focusses on the systems of interest and only the events that introduce or remove them and therefore affect the capability realised.

Other Frameworks

See also:

References

 


Category:Framework -> Viewpoint
Category:Framework -> Specification
Category:Procurement
Category:Acquisition

Categories:

  • Procurement
  •  

    © 2010 Eclectica Systems Ltd.