Practise-6 Software modeling Objectives

Constraints(cheklov)
The constraints are the limitations of the system. In this case, the constraints would include:

• 
  The types of clothes that can be sold.
  
• 
  The payment methods that are accepted.
  
• 
  The shipping methods that are offered.
  
• 
  The age restrictions for the website.
  

Modeling Graphs
Here are some modeling graphs that can be used to represent the different aspects of the online shopping project for selling clothes:

• 
  A UML class diagram that shows the different classes of objects in the system.
  

Figure-4. Class diagram example of Online Shopping project

• 
  A UML sequence diagram that shows the sequence of steps involved in a use case.
  
• 
  
  

Figure-5. Sequence Diagram - Online Shopping

• 
  A UML activity diagram that shows the flow of control in a process.
  

Software models can be created using a variety of tools, including:

• 
  Whiteboard: Whiteboards are a simple and effective way to create and share software models.
  
• 
  Diagramming tools: Diagramming tools such as Lucidchart and Draw.io provide a variety of features for creating and editing software models.
  
• 
  Integrated development environments (IDEs): IDEs such as Eclipse and Visual Studio provide features for creating and editing software models, as well as for generating code from those models.
  

There are given some of the benefits of software modeling:

• 
  Improved communication: Software models can help developers to communicate and document the design of a software system in a clear and concise way.
  
• 
  Reduced errors: Software models can help developers to identify and correct errors in the design of a software system before it is implemented.
  
• 
  Increased productivity: Software models can help developers to generate code from the design of a software system, which can save time and effort.
  
• 
  Improved maintainability: Software models can help developers to understand the design of a software system, which can make it easier to maintain and update the system.
  

Questions.

1. 
   What is software modeling ?
   
2. 
   What are static and dynamic modeling ?
   
3. 
   Do you know about system boundary ?
   
4. 
   Do you know about use cases ?
   

References.

1. 
   Hassan Gomaa (2011). Software modeling and design. Pages 71- 92.
   
2. 
   Hassan Gomaa (2011). Software modeling and design. Pages 3-12.