Showing posts from September, 2008

Project Network Diagram Information and Data

The information and data needed to document a project network diagram is obtained by calculating and analyzing dates, estimating durations, and, if needed, cross-reference data from the WBS (Work Breakdown Structure). These tasks should be (and mapped into) the lowest level of the WBS, i.e., at task level. Operationally, this diagram represents the dynamics of the project, i.e., how the tasks are placed in relation to each other, with respect to time and effort. No single taks can be placed pending whithin the project network diagram.

Build and Deploy a Project using OO technology

Once the process of analyzing and gathering requirements is completed ( least one iteration), then it's possible to proceed to the next phase: building the application.

-Modelling has to do with designing the technical architecture in detail. From use cases it’s possible to create object models and sequence diagrams to describe the static and dynamic nature of the application.
-Here there is a need to create deployment diagrams that describe the tiers and processing nodes required to support the application.
-During this process there is a need to create the information architecture and illustrate how it ties to the data dictionary, navigation features and content types into a cohesive site map.
-The information architecture is created with the use of user scenarios, storyboards and site maps that precisely describe the interface before the project moves to the build stage.
-The Interface Design is driven by the use cases that describe the requirements of system…