This chapter describes how to work with RePoSyD based on the use case “How we want to use RePoSyD?”. The use case is deliberately not technical, since it is always difficult to find an example of a technical system for which none of the people involved has detailed knowledge.

The following example “How do we want to use RePoSyD?” is essentially about the implementation of RePoSyD in an organization in a company or, to stay in the SE terminology, the system “company”. This may sound strange in the first step, since we as engineers would put the term “system” in a technical context in most cases.

In systems engineering, however, the term is much broader defined;

A system is a set or arrangement of elements [people, products (hardware and software), and processes (facilities, equipment, materials, and procedures)] that are interrelated and whose behavior satisfies customer/operational needs and ensures the maintenance of the life cycle of the products.“IEEE 1220 3.1 Definitions

As already mentioned, the use case is about the introduction of RePoSyD in the organization of a company. Analogous to the development of a technical system, the required process steps are run through and in parallel the capabilities and functions of RePoSyD are used. I.e. to plan the project, to control and monitor the execution, and last but not least to determine the requirements of the organization for RePoSyD and to define RePoSyD as a component of the system “enterprise” with its required functions and interfaces. The Organization

The organization is a small company with about twenty odd employees. Your team includes a total of three colleagues, John and Jane Doe, and of course yourself (the Admin). Your tasks include the planning as well as the execution of the project. In parallel, you shall save all relevant results in RePoSyD in order to gain experience in the application of the tool.

Other employees include:

  • Dilbert - The IT manager
  • Wally - The man who tries to catch up with the work, but always remains the decisive step behind.
  • Dogbert -
  • Ratbert and Bob - The first to work with RePoSyD.

As a result, the requirements of the organization shall be summarized in a System Specification and the integration of RePoSyD into the existing IT infrastructure shall be described in a System Description.

Please do not forget that the example does not claim to be complete, nor does it represent a cookbook for the necessary implementation of RePoSyD in your organization. With or without tools, the implementation of systems engineering in an organization is always a “hard work” and depends on all stakeholders in your organization.

This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
  • manual/uc/start/start.txt
  • Last modified: 8 months ago
  • by maho