Computer Science and Engineering Department Haryana College of Technology and Management(kaithal) Seminar Report on Workflows Of The Process Anuj Chaudhary CSE 1706239
Process Description Most process description uses sequence of activities as there primary representation format. Sequentially oriented representation are easy to understand,represent.plan and conduct. However this sequential view is not applicable on software projects that are team efforts. In team process,progress is made on different artifacts that must be synchronized,crosschecked,merged and integrated.
This distributed nature of the software and its subordinate workflows becomes the primary source of complexity. One of the more subtle flaws in the conventional software process was in presenting the life cycle macroprocess as a sequential thread of activities, going through the following stages: Requirements Analysis Design Code Delivery
Modern Process Modern process avoids naming the life cycle phases after the predominant activities. The phase names are given as: Inception Elaboration Construction Transition The intent is to recognize explicitly the trend of activities in all phases and to avoid the interference that there is a sequential progression from requirement to design to code to test to delivery.
Software process Workflows The macro process comprises of discrete phases and iterations, but not discrete activities. A set of activities occurs in each phase and iterations.The next level process description is the microprocesses,or workflows. The term Workflow is used to mean a thread of cohesive and mostly sequential activities. Workflows are mapped to product artifacts. Artifact represents cohesive information that typically is developed and reviewed as a single entity.
Software Process Workflows There are seven top-level workflows: Management workflow: controlling the process and ensuring win conditions for all stake holders. Environment workflow: automating the process and evolving the maintenance environment. Requirements workflow: analyzing the problem space and design artifacts. Design workflow: modeling the solution and evolving the architecture and design artifacts.
Software Process Workflows Implementation workflow: programming the components and evolving the implementation and deployment artifacts. Assessment workflows: assessing the trends in process and product quality. Deployment workflow: transitioning the end products to the user.
Principles of Process Workflows Architecture-first approach - Extensive requirements analysis,design,implementations and assessment activities are performed before the construction phase, when full scale implementation is the focus. This early life-cycle focus on implementing and testing the architecture must precede full scale development and testing of all the components and must precede the downstream focus on completeness and quality of the entire of the entire breadth of product features. Iterative life-cycle process. Some projects may require only one iteration in a phase; others may require several iterations. The point that the activities and artifacts of any given workflow may require more than one pass to achieve adequate results.
Round-Trip engineering. Raising the environment activities to a first class workflow is critical. The environment is the tangible embodiment of the project’s process, methods, and notations for producing the artifacts. Demonstration based approach. Implementation and assessment activities are initiated early in the life cycle, reflecting the emphasis on constructing executable subsets of the evolving architecture.