OBJECT ORIENTED VS STRUCTURED WHICH ONE IS YOUR CHOICE

OBJECT ORIENTED VS STRUCTURED Choosing between Object oriented or structured is confusing The perfect question is to ask which one is suitable for your project

QUESTION NEED TO ASK YOURSELF How familiar are you with the method How complex is your project Which method is suitable to analyze and design your system What kind of tools you using for your development Is there any preference or evaluation bonus on choosing a method

STRUCTURED APPROACH Structured Approach to developing a software application involves the use of p

STRUCTURED APPROACH Logical steps of System Development Life Cycle – Analysis, Design and Implementation. Fewer models. Steps are documented clearly at the end of each phase. Focus more on business aspect of a system. Deals with other component separately. Top-down approach in understanding problem.

STRUCTURED APPROACH (CONT) Process models are the focus of understanding user requirements. Design models are easier to extract from analysis model. Easy to extract design information. Does not dictate any model for development environment. Easy to manage system development project.

OBJECT ORIENTED It is developed by the software engineering professionals who deal with large and complex systems in domains such as aerospace and process control (Schach, 2004). The object-oriented methodology views a system as a bottom-up approach to systems development. To start with, it describes the system through a set of business processes it performs as well the object classes that these processes deal with. It uses a set of diagrams or models to represent various views and functionality of a system and is commonly known as Unified Modeling Language or UML

No logical steps of SDLC – repeating all phases during each iteration. Many models to deal with (13 diagrams & models). OBJECT ORIENTED (CONT.)

There are no documents per see; all information is contained within the model descriptions. Starts with the business aspects of a system but deals with other components such as user interface, network architecture, processing architecture together as the analyst moves from the requirements models to design models. Bottom-up approach of understanding a problem through process definition and data definition. Use cases are the focus of understanding user requirements. Design models depend on many analysis models Very complex to extract design information for systems components such as user-interface, application programs, and database or files. There layer approach to systems design is closely analogous to development environment Not easy to manage systems development project as models require continuous revisiting and the hardest part which is programming that depends on packages (are complex) ; thus task duration is hard to quantify. OBJECT ORIENTED (CONT.)

CREATE A TABLE TO EVALUATE From the previous question that stated, create a table and give a scale from 0 to 5. 0 mean lower rate and 5 is the highest rate ParametersObject OrientedStructured Familiarity with the method 53 Suitability with the project42 Tools available42 Extra bonus either method00 Total mark97

CREATE A TABLE TO EVALUATE The table from previous slide that we create shows that, its more suitable to use Object Oriented method rather than structured method. If the total value is equal then you can freely choose either one.