Systems Modelling Theory - Essay Example

?SYSTEMS MODELLING THEORY Systems Modelling Theory Affiliation Introduction This paper is based on is a discussion about a scenario presented by my company’s coordinator. In this paper I have been asked to develop a company response for the following systems modelling theory issues that are to be incorporated into a response to a Request for proposal (RFP). This paper presents an overview of systems modelling theory. This paper also presents some of the associated concepts to prove that the company really knows systems modelling theory. An overview of Systems Modelling Theory System modeling is commonly used software engineering practice that demonstrates, visualize, evaluate and convert the architecture of a system from one domain to another. In this scenario, a system can be used to denote different entities such as software system or its different parts, hardware system, or it can be a combination of both and the relationships between these parts. Hence, a system model can be recognized as a skeletal model of the system. In addition, system modelling provides an excellent support throughout the development and maintenance large and complex systems by paying a great deal of attention to the system development phase. In this scenario, the basic thought is to capture unstable or complex elements of a design within different parts through appropriately designed interfaces showing how each part communicates with its surroundings. Later on, these separated parts are combined in order to develop a complete system (Kresken, 1996; Pidd, 2004, p. 14). It is an admitted fact that systems modelling theory is capable of improving systems’ performance and reliability and minimizing systems development expenses as it makes the system development process very simple. For instance, it allows us to make use of previously developed components and routines to develop new systems. It also allows us to make changes to systems according to changing requirements for instance platform changes and functional enhancement, and to completely understand systems. Hence, we can say that systems modelling theory allows us to deal with a wide variety of requirements as it offers a set of tools like that consistency checkers, helps with documentation of the system and even we can also use it in the design stage of system development. To cut a long story short, system modelling technique is utilized to make sure that a developing component of software develops in a constant way and that it simplifies the process of combining different software parts (Kresken, 1996; Pidd, 2004, p. 14). In addition, in order to model a system there is need of a system modelling language (this language can be either textual and/or diagrammatic) and a theoretical structure. In fact, at the present there are many tools available that support system development through systems modeling theory. The majority of these tools use textual notations such as prose or tables, diagrammatic notations like graphs. Additionally, these diagrams use different symbols to symbolize the components of the system for instance objects, entities, and groups of objects, and a wide variety of other symbols representing the relationships between these components. In the past few years, four major theoretical structures have emerged: (Kresken, 1996; Pidd, 2004, p. 14) 1. Design Methods Design methods are based on a set of three components a concept, a language, and a design process. In this scenario, the concept outlines the modules of a program that are to be symbolized by the parts of the system model. On the other hand, the language defines the system model. Additionally, the system designer would have to follow a step-by-step procedure in order to compile design of the system in accordance with the software lifecycle. Moreover, there are many design methods which can be used for different purposes such as task design that is particularly developed for dealing with processes and their interactions, and synchronized systems design (Kresken, 1996; Pidd, 2004, p. 14). 2. Module Interconnection Languages (MILs) Developing system components and establishing relationships between them in an attempt to build a large system require different design efforts. In this scenario, module interconnection languages (MILs) are used to support connection effort of large and complex systems. In addition, module interconnection language can be acknowledged as a structural design language for the reason that it describes the system modules and how they are connected with each other to make the system (Kresken, 1996; Pidd, 2004, p. 14). 3. Software Architectures In view of the fact that increasing specification and design, complexity and size the overall system structure turns out to be more important than the selection of data structures and algorithms thus in order to deal with these issues and requirements, software architectures are being created. These architectures will provide an excellent support for software development process (Kresken, 1996; Pidd, 2004, p. 14). 4. Design Patterns As compared to above discussed system modeling techniques, design patterns are the most theoretical methodology to model a system and its behaviour. It is believed that design patterns are similar to software system architectures, regardless of a particular programming language and tool or a language concept such as modular or object-oriented programming. At the present, this system modeling technique is utilized to balance previously implemented design methods by providing solutions to problems that are far beyond the reach of those methods. However, each design pattern provides a solution for a specific object-oriented design problem. In this scenario, design patterns should not be considered as a mechanism to build systems or their components. However, design patterns correspond to a more common depiction of how to build a system or components of a system (Kresken, 1996; Pidd, 2004, p. 14). 5. Prototyping Approach As discussed above, there are different approaches to modeling a system. In this scenario, a prototype is also one of the most effective system modeling techniques. Basically, a prototype is working model of a system or a subsystem that has to be developed by the system development team. However, the basic purpose of this model is to collect information about the user’s requirements by providing them a working model with which they can interact. To all intents and purposes, the prototype is believed to be an initial version of the expected system or component from which requirements are gathered and on which later versions are based (Davis & Yen, 1998). In fact, this system modeling technique can support the well-organized development of software systems by dividing a large and complex, and frequently unclear problem into a number of wide-ranging yet simpler and smaller components. In addition, this system modeling methodology allows us to develop, and then improve, a software item to convene end-user’s expectations (Carr & Verner, 1998). 6. Brainstorming Similar to above discussed techniques, brainstorming is also a most important system modeling technique as it can help resolve disputes and confusions over requirements. In fact, it clarifies what has to be developed. It gives a clear view of the system requirements. Basically, the brainstorming is the process of getting ideas, views, and explanations to a question or confusion in a meeting environment in which all the team members and stakeholders are given the opportunity to raise questions and share their ideas. In addition, in a meeting session all the stakeholders are encouraged and have a tendency to instinctively formulate a number of good ideas, supported by what others have stated reserved or timid people can explain their ideas well in view of the fact that anonymity can be confident. At the present, agile software development methodologies fully support brainstorming (University of Ottawa, 2013). 7. Skepticism and testing during model design It is believed that at the stage of skepticism many developers focus on adding a large amount of functionality into the system with the intention that they can create systems with sufficient usability and that focusing particularly on usability aspects will be a waste of time. However, it is good practice to pay attention to initial usability practices at building understanding and obligation to usability, rather than trying to obtain the possible results. Hence, it will be difficult for skeptical developers to obtain optimum results (Erdogmus & Tanir, 2002, p. 90). We will focus on adding more usability features in our design so that it becomes easy for the customer to test it. We will apply different testing techniques to design in order to achieve effective output. 8. Handling of multiple breakeven points Break-even points are a major determinant of a business model and software development projects. However, they vary from organization to organization. For instance, the organizations with a higher break-even point need to create and deliver software products that catch the attention of a broader customer base. In this scenario, it can drive decisions regarding system designs and features toward the bland. In addition, the software products with lower profit margins and prices increase a company’s breakeven point however; they can sell a large number of products to a large customer base in order to generate maximum revenue. On the other hand, in case of lower breakeven points, we can target smaller, more attractive niches rather than the broader market. In this scenario, we can customize our software products and associated services to those particular needs, by giving more value to the customers. Moreover, giving more value to our customers will help us develop greater brand equity, with encouraging response on value, profit margin and share (Gazelles, Stark, & Stewart, 2013). For our company, we will handle both kinds of breakeven points. We will tailor our services according to the nature of the software project. References Carr, M., & Verner, J. (1998). Prototyping and Software Development Approaches. Retrieved February 04, 2013, from http://rguerrero334.blogspot.es/img/Prototyping_and_Software_Development_Approaches.pdf Davis, W. S., & Yen, D. C. (1998). 31 Prototyping. Retrieved January 30, 2013, from The Information Systems: Analysis and Design: http://www.hit.ac.il/staff/leonidm/information-systems/ch31.html Erdogmus, H., & Tanir, O. (2002). Advances in Software Engineering: Comprehension, Evaluation, and Evolution. New York: Springer. Gazelles, H., Stark, K., & Stewart, B. (2013). 3 Ways to Lower Your Break-even Point. Retrieved February 04, 2013, from http://www.inc.com/karl-and-bill/3-ways-to-lower-your-breakeven-point.html Kresken, T. (1996, September 15). Technology Briefing Report System Modelling: RENAISSANCE Esprit Project 22010. Retrieved February 03, 2013, from http://www.comp.lancs.ac.uk/computing/research/cseg/projects/renaissance/RenaissanceWeb/project/Acrobat/System_Modelling.pdf Pidd, M. (2004). Systems Modelling: Theory and Practice. John Wiley & Sons. University of Ottawa. (2013). Brainstorming. Retrieved February 04, 2013, from http://www.site.uottawa.ca:4321/oose/index.html#brainstorming Read More