Software Engineering

Software Modeling

The practice of creating and analyzing software models. Software modeling should address the entire software design including interfaces, interactions with other software, and all the software methods. Technically Software Modeling is the process of developing any aspect of a software system such as requirements, architecture, behaviour and analyzing what software can do, benefits, scope and limitation.

Software Modelling Techniques:

Pseudo-code: The original software model. Has an origin in mathematics

Flowcharts: Mid 20th century. Probably came from the business world, used to visually model processes, business logic.

Specification & Description Language (SDL): 1976. Describes state machines, events and constraints, used by telecom industry to validate WAN protocol stacks

Message Sequence Charts (MCS): Mid 80's. Describes sequence of state changes and communications between objects/modules

Behavior Modeling

Behavior modeling is when you think of your ideas in terms of states and transitions. This requires both identifying all of the interesting states of being that your software or its components are likely to be in. And also, at a high level, abstracting what events are likely to cause your software or its components to change between states of being. Behavioral Modeling contains a set of tools for performing a wide variety of analysis on a model and incorporating the analysis results into the model. Behavioral Modeling lets you modify the model design to reflect the desired solution. You use the Behavioral Modeling tools to:

•Create feature parameters based on measurements and analyses of the model.

•Create geometric entities based on measurements and analyses of the model.

•Create new types of measurements tailored to application-specific needs.

•Analyze the behavior of measured parameters as variable dimensions and parameters change.

•Automatically find dimension and parameter values that achieve a desired behavior of...