Week 3: Tutorial Scenario Roselle

 

For this week, Sir Zaki gave us to see a video of a process on making roselle jam and syrup. From that video, we were given tutorial to make a context diagram, flowchart and block diagram based on the process of making the roselle jam and syrup.

First, a context diagram, sometimes called a level 0 data-flow diagram, is drawn to define and clarify the boundaries of the software system. It identifies the flows of information between the system and external entities. The entire software system is shown as a single process. We produced a context diagram containing data, signals, materials, energy and activities. Below shown is the context diagram produced.

 


Next, a flowchart is simply a graphical representation of steps. It shows steps in sequential order and is widely used in presenting the flow of algorithms, workflow or processes. Typically, a flowchart shows the steps as boxes of various kinds, and their order by connecting them with arrows. We were assigned to produce a flowchart of the process involved to produce bottled jam. Below shown  is the flowchart produced.

 



Finally, a block diagram is a diagram of a system in which the principal parts or functions are represented by blocks connected by lines that show the relationships of the blocks. For this task, we need to design a manufacturing process for a SME factory to produce 10,000 bottles of syrup and 5,000 bottles of jam per day. Below shown are the block diagram produced.

 



Analysis for this week: We've learned that each change requires that you start from the beginning and work through the entire sequential process. In order to thrive in the current marketplace, we need to change the way value is delivered in the products, we can start to re-examine our product planning, management, and development processes. For example, in order to satisfy the need to produce 10,000 bottles of syrup and 5,000 bottles of jam, we need to design a system that can meet the requirements for the jam and syrup to be produced according to the amount required.

Comments

Post a Comment

Popular posts from this blog

Week 15 - Operational Architecture on Capella.

Image
           For this week, we design the operational architecture of the automatic bread-making machine using Capella. The steps of the process are followed on the Capella website. The first one is the Operational Entity Breakdown.  The operational actors in this section are the oven and mixing machine. These operational actors are going to interact with the operational entities. On the right is the operational entities. The ingredients below like sugar, salt, yeast, and water are contained in the dough. The next one is operational Capabilities. In this section, the operational capability is named “Make Bread”. Below the operational capability are the operational entities. The operational capability is showing the involvement of the mixing machine and the oven.          Next is the Operational Entity Scenario. In this process,  We define and allocate the activities to the operational entities or actors and then we define all the interactions of the activities. After that is Operational
Read more

Week 10 - Capella Tutorial.

Image
         For  this week, we learn how to using Capella Project during the tutorial period. Dr. Zaki was asking each group member to do the tutorial.  We use this application because it can match the criteria at the end of the project based on the format of Prof. Zul given.           The Capella workbench provides methodological guidance, including an engineering workflow with clear modeling objectives, and an advanced set of productivity tools. It helps us to do the block diagram for our project. We can see the advantages of these applications.                Capella is a concrete illustration of an open and field-proven approach that can solve major concrete industrial challenges. Its creators decided to capitalize on Eclipse Modeling and its ecosystem to implement the adaptable and extensible workbench that could both support the MBSE approach it required and fit the specific needs of the company’s business units.           Capella also benefits from the PolarSys Working Group i
Read more

Week 11 - System Architecting

Image
     For this week, we learned about system architecting  is the conceptual model that defines the structure, behavior, and more views of a  system . An  architecture  description is a formal description and representation of a  system , organized in a way that supports reasoning about the structures and behaviors of the  system .  Architecture is associated with structures, their relationships, and expectation for their design. This applies to complex systems, such as aircraft, power plants, and spacecraft, as much as buildings.       There are three types of architecture. The first is functional architecture. Functional  architecture  is an  architectural  model that identifies system  function  and their interactions. It defines how the functions will operate together to perform the system mission. Generally, more than one  architecture  can satisfy the requirements.  Below shows an example of a glucose meter functional architecture.           The second type of architecture is phy
Read more