Essay: Object-oriented Software Development For System Requirements: Iterative Approach." (70 Characters)

Have a comprehensive understanding of the role of the systems analyst/ designer, the context in which the systems development activity takes place and the professional standards that are applied to the activity.

System designing process is required different approaches for solving and understanding the basic requirements. Object-orientated (referred as OO) Language is a procedural language, which is used for designing of a system. It provides object oriented concepts for making use case diagrams from system requirements, which are given by the client. It is suitable approach for large-scale projects. It is a graphical way to apprehend mission requirement as well as converting them to a software code (Bruegge, 2008).

It is particularly used in modern-day software program development processes. It affords usability in software improvement. Software development process is widely growing at present time for large-scale software designing. It has far noticeably demanded at special levels, along with industrial, social, and commercial organizations. Numerous projects got failure because of less understanding of requirements, which is based on the requirements of system. It is a process for avoiding faults of developer. OO strategies are used for information records flow and manage go with the process of the project (Conallen, 2012). This file will discuss about the iterative approach of object-oriented process in this report.

Object oriented process is used for large-scale systems development. This method is used iterative approach for dealing software development process. Object-oriented approach is imparting answer for software improvement in exclusive patterns, as examine to other strategies. UML is based on this approach. It gives extraordinary notations for understanding waft of and manipulate within the device. Software development is so necessary for different organizations (EXISTEK, 2017).  

Business process model is simple approach of understanding data flow and control flow of a system. It is like flow chart of a system.  In present existence style all works are require assist of information technology. Object orientated systems are required few matters for amendment inside the necessities. Software program development is a procedure, which is having many phases are executed at the end of developer. However, analysis is the first step for starting the system development. Necessities are needed for software program improvement (Gomaa, 2011).

Many projects are failed due to loss of requirement expertise. Developer also faces a few issues from the requirements of a system. Those are the reasons consumer’s desires, converting requirements, go with the flow of statistics, and control. These are few inconsistencies in the client’s requirements. Some of the issues in necessities can be prevented at designing time and development time of a project. UML notations are helpful for the understanding of software requirements (Jacobson, 1993).  

Object orientated method is used for the designing of the system. In this method, items are times of instructions. It is miles a way to get entry to the records though a summary system. It is similar like float charts. OO approach is applied for UML designing. UML changes basic requirements to the use cases for better understanding. UML is having nine different notations for handling requirements (Larman, 2012).

There are few steps for identification of classes. Use case diagrams are helping in identification of classes. It is so simple process but identification is so important process.  Entity based approach is also useful for handling the identification of classes. Entities are specified in the use case diagrams and it will also changes in the classes in the class diagrams. Collaboration of entities with their attributes is also important for identification of classes (Liang, 2003).

Conclusion

Iterative method is needed more assets then different strategies. It has far required consistent management. It makes use of quick making plans ranges with a view to create issues with the architecture, and not all the necessities are fulfilled. On this method, dangers will not determine at the end of the project, because of that it required a relatively certified professional. It is not appropriate for the small tasks. It is also include different things, which makes it easy for the designers, together with instance of training, use instances ( Oliver, 2017).

Developer required a clear and clean understanding of project, so there are no changes from the client side. It is also necessary for the client as well as developer. UML is having a quality of solving these types of system designing. There are so many methods for identification of classes. Iterative approach is best for identification of software classes, because of their working model. It takes classes on behalf of entities, attribute, and collaboration of use cases to the actors (Powell-Morse, 2017).

Class diagram are a basic architecture for a system development. It is having a clear scenario for understanding a code of project in form of diagrams. It is also having conversion facility for code generation (Satzinger, et al., 2011). Iterative method is facing few problems of code optimization. Code optimization is a process in which class diagrams are converted in to a code, and vice-versa. There is a huge problem if any class is missing from the basic requirements of the client. Few functions are must for the projects, so selection of classes is also an important part for system designing (Van Lamsweerde, 2009).

UML diagrams are sometimes not having use, because of their complexity. There is a reason for all the diagram or notations of UML designing. There are few things, which are never missing from the class diagrams. Sometimes data flow is creating an issue in the project, because of lack of understanding about the requirement. Use cases are mainly useful for creating class diagram.         

Conclusion 

This report is concluded that object oriented approach are having best results for the identification of classes. There are so many iterative methods for finding classes from the use case diagrams. Business process approach is the first step in which connection is made with activities and actors of the system. There is some reverse process of classes’ conversion. It is also having some methods for changing the classes from the entities of the given requirements. There are basic rules for accessing classes from the requirement. Use case diagram is a coupling of system requirements, and class diagrams are decoupling of use case diagrams.   

Finally, it is concluded that object-oriented software development process is beneficial for large-scale projects, but it is not fit for small projects. It is best approach for identification of classes from the system requirements, which are provided by the client.

Object oriented software development model is following the iterative approach for classes designing on the bases of software requirement. It is a best method for identification of classes from the use case diagrams. Business process model is basic model for identification, such as flowcharts. Iterative approach is best approach for the identification of classes from the system requirements. It is a systematic process in which analysis of classes is first step and it start with it. It identifies classes based on entities and attributes of the use cases.

Use case diagrams are coupling of different use cases and actors. It is a relationship between the actors and use cases. It is also showing data flow and control flow of project. Class diagram is decoupling of use case diagram. Class diagram is directly converted into a software code, so it is important that every class should have a reason behind it.

Code optimization is also a problem in case the developer does not do proper selection of classes. Use cases are just a brief about the functioning of system requirement. It is also having few best concepts for converting class diagrams into a software code in a programming language.

Iterative model is best for the finding classes from the use case diagrams. It provides best classes on the bases of use cases and their specification with the entities. There are few steps for testing of classes, which can help for reducing code optimization issues in the code, which is generated using classes.

References

Oliver, R., 2017. Why the Software Industry Has a Love-Hate Relationship with UML Diagrams. [Online] Available at: https://creately.com/blog/diagrams/advantages-and-disadvantages-of-uml/[Accessed 17 November 2018].

Bruegge, B. a. D. A., 2008. Object-Oriented Software Engineering Using UML, Patterns and Java-(Required) (Vol. 2004).. 4 ed. London: Prentice Hall..

Conallen, J., 2012. Building Web applications with UML.. 6 ed. New York: Addison-Wesley Longman Publishing Co., Inc...

EXISTEK, 2017. SDLC Models Explained: Agile, Waterfall, V-Shaped, Iterative, Spiral. [Online]
Available at: https://existek.com/blog/sdlc-models/
[Accessed 22 November 2018].

Gomaa, H., 2011. Software modeling and design: UML, use cases, patterns, and software architectures.. 2 ed. New York: Cambridge University Press..

Jacobson, . I., 1993. Object-oriented software engineering: a use case driven approach.. 2 ed. New Delhi: Pearson Education India.

Larman, C., 2012. Applying UML and patterns: an introduction to object oriented analysis and design and interative development.. 5 ed. New York: Pearson Education.

Liang, Y., 2003. From use cases to classes: a way of building object model with UML. Information and Software technology, 45(2), pp. 83-93.

Powell-Morse, A., 2017. Object-Oriented Analysis and Design: What is it and how do you use it?. [Online] Available at: https://airbrake.io/blog/design-patterns/object-oriented-analysis-and-design
[Accessed 22 November 2018].

Satzinger, . J. W., Jackson, R. B. & Burd, S. D., 2011. Systems analysis and design in a changing world. 6th ed. New York: Cengage learning..

Van Lamsweerde, A., 2009. Requirements engineering: From system goals to UML models to software (Vol. 10).. 2 ed. Chichester: John Wiley & Sons..