Everand Logo

Welcome to Everand!

  • Discover millions of ebooks, audiobooks, and so much more with a free trial

    Only $11.99/month after trial. Cancel anytime.

    Software Engineering & Object Oriented Modeling
    Software Engineering & Object Oriented Modeling
    Software Engineering & Object Oriented Modeling
    Ebook201 pages1 hour

    Software Engineering & Object Oriented Modeling

    By Jitendra Patel

    ()

    Read preview

    About this ebook

    Software Engineering and Object Oriented Modeling: This book is specially written for those who are interested in understanding software engineering and Object Oriented Modeling concepts using UML in the Computer Engineering and Information technology field and want to gain enhanced knowledge about the power of UML Language in software development.

    Also everyone with interest in learning UML for Software Engineering for application development can refer to this book to get the knowledge about various features of this subject.
    LanguageEnglish
    PublishereBookIt.com
    Release dateApr 26, 2016
    ISBN9781456612542
    Software Engineering & Object Oriented Modeling

    Read more from Jitendra Patel

    Related to Software Engineering & Object Oriented Modeling

    Related ebooks

    Programming For You

    View More
    View More

    Related podcast episodes

    Related articles

    • Article

      Create Smaller Sized Apps With React

      Nov 19, 2019

      You may not be surprised that some developers have criticised Electron (see tutorials LXF256), mostly regarding the memory usage of its final binaries. The initial binary is over 100MB, because a major chunk of code from Chrome is embedded. When you

      6 min read

    • Article

      Code An Admin Back-end In Django

      Dec 13, 2022

      Credit: www.djangoproject.com OUR EXPERT Matt Holder has been a fan of the open source methodology for over two decades and uses Linux and other tools where possible. More featurepacked source code for this project can be downloaded from https://

      6 min read

    • Article

      Access Your Mac Anywhere

      Nov 8, 2022

      Access Your Mac Anywhere
      2 min read

    • Article

      Mailserver

      Oct 19, 2021

      Mailserver
      3 min read

    • Article

      Rise Of The Robots

      Jan 12, 2021

      Rise Of The Robots
      7 min read

    • Article

      Rokoko Studio 2.0

      Feb 23, 2021

      Rokoko Studio 2.0
      1 min read

    • Article

      Installation

      Oct 19, 2021

      Installation
      1 min read

    • Article

      » Stochastic Algorithms

      Dec 14, 2021

      If you’re up for some relatively maths-heavy computer-science reading (and who isn’t?), then consider looking into stochastic algorithms. Sometimes lumped together with machine-learning, stochastic algorithms is a loosely defined category that you co

      1 min read

    • Article

      Charts And Diagrams

      Nov 15, 2022

      Charts And Diagrams
      1 min read

    • Article

      Assessing Ease Of Use

      Jul 28, 2020

      Assessing Ease Of Use
      3 min read

    • Article

      Getting The edge

      Feb 25, 2021

      Getting The edge
      7 min read

    • Article

      Putting Your Words In Order

      Jun 3, 2021

      Putting Your Words In Order
      5 min read

    • Article

      Microcontrollers In Amateur Radio

      May 1, 2022

      When you hit the compile button for your compiler, there’s a whole bunch of stuff that takes place that isn’t obvious while the code compiles. In general terms, the C compiler: 1) invokes a preprocessor pass on the code;2) performs syntax/semantic ch

      4 min read

    • Article

      A.i. Coding

      Aug 22, 2023

      A.i. Coding
      16 min read

    • Article

      Code A Cataloguing Application In Python

      Nov 15, 2022

      Credit: www.djangoproject.com Matt Holder has been a fan of the open source methodology for over two decades and uses Linux and other tools where possible. More featurepacked source code for this project can be downloaded from https://github.com/mat

      8 min read

    • Article

      Make AI Work For You

      Apr 2, 2024

      Make AI Work For You
      8 min read

    • Article

      Going From RDC To PGC

      Jun 1, 2021

      This month, Arduino guru Jack Purdum, W8TEE, sits in as Guest Columnist. Working with microcontrollers often requires more than a soldering iron … while many microcontroller projects use computer code already written by someone else, it is sometimes

      8 min read

    • Article

      Computer-aided Design

      Jul 25, 2023

      Computer-aided Design
      13 min read

    Related categories

    Reviews for Software Engineering & Object Oriented Modeling

    0 ratings

    0 ratings0 reviews

    What did you think?

    Tap to rate

    Review must be at least 10 words

      Book preview

      Software Engineering & Object Oriented Modeling - Jitendra Patel

      References

      Chapter 1 Software Engineering: Disciplined Software Development

      Why is software engineering different from programming?

      According to the IEEE definition, software engineering is the application of a systematic, disciplined, quantifiable approach to the development, operation and maintenance of software that is, the application of engineering to software. 

      Disciplined approaches to software development are gaining greater acceptance in practice these days. This is especially true in projects where safety is absolutely critical, such in airplane control software, or where a software crash could cause a major foul-up such as in the telephone system. But it is also true in general as software developers strive to achieve higher levels of maturity on the Software Enterprise Institute’s (SEI ) scale  (Figure 1).

      Figure 1  The SEI Levels of Maturity

      The SEI hierarchy is a model of achievement that is becoming widely accepted as a credential necessary to qualify to bid on a contract. So it is important that students not only  have the basic programming skills but also the understanding of formal principles that enable them to fit into high SEI-ranking software organizations.

      Object-orientation provides a powerful way to build complex software systems, a claim supported by the overwhelming adoption of C++ and Java as programming languages of choice, with installations in the hundreds of thousands. Nevertheless, a programming language by itself does not provide a set of sound principles to use -- you can  just as easily program poorly in C++ as in its non-object-oriented predecessor, C. Thus, this course offers principles for object-oriented system  development that guide the effective application of object-oriented programming constructs.

      Technology Invariance and Skills Survival

      Technology is moving toward increased networked and distributed computing and this will certainly influence the programming language standard. Java currently is the object-oriented language for World Wide Web programming. But standards and specifications are more permanent than languages and technologies.  We can see this as the premise underlying the effort to define a Common Object Request Broker Architecture (CORBA). This effort, supported by many of the world’s leading information age companies, is to provide workable specifications that will enable objects to interact by adhering to common interfaces while hiding the details of their implementations (vendors, languages, technologies, etc.).

      Principles are even more permanent than specifications. So the concepts  we present here, while shown to work in C++ and Java, are also aimed at future languages,  technologies and systems that are likely to be distributed, parallel and global.  They will help you surf with the waves of technology change that can be expected in the next century.

      Towards a Disciplined Realistic Software Development Process

      What distinguishes a principled software engineering process from programming practice? A series of diagrams will suggest the answer. Figure 2 caricatures our natural programming tendencies. There are three steps:

      conceptualize:  think about the problem

      write code: express your ideas directly in programming form

      debug: execute and modify the code until it does what you want

      Figure 2 Common Programming Practice

      On the other hand, software engineering texts prescribe methodologies for software development that are much more disciplined.  Figure 3 illustrates one version of such a methodology. According to it you should:

      1.     formulate requirements to express the desired behavior the software

      2.     specify: express the behavior exactly

      3.     concurrently

      ·         implement: write code that realizes the desired behavior

      ·         develop test plan: design tests that reveal whether the code   actually does realize the desired behavior

      4.     debug: correct the flaws revealed by the tests until they are all satisfied

      Figure 3 Idealized Software Development Process

      This scenario imagines that you can think through all of the situations encountered by the software application and say what it is expected to do in each. Having done this, you can proceed to implement the system in coded form. Now, since the desired behavior has been precisely defined, tests can be developed based on it before actual implementation. So after both have been completed, the tests are executed on the implemented system. This can be called a waterfall model since the work progresses down stream with no reversals.

      The waterfall model has, alas, become the model that methodologists love to hate. Ordinary people just can’t practice what it preaches and numerous amendments to it have been proposed that are more in keeping with what humans can do. Nevertheless, the individual phases it identifies are essential to principled development of object oriented software. However, rather than require that they be carried out in rigid order, we view the situation as in Figure 4. We are constantly conceptualizing the problem, getting a better understanding of it, as we iterate through the phases. You may or may not succeed in exactly specifying the desired behavior at first, but this attempt puts you in a much better position to implement the code since you have a well-thought out blueprint to guide you. When you develop the test plan based on the specification you may notice some things wrong with it: nothing prevents, you from going back and modifying the specification accordingly. The same goes for revisiting any of the phases. Having a good test plan makes the process of debugging much more efficient than the conventional way of doing it and the resulting software much more reliable.

      Figure 4 More Realistic Process

      This course will help you understand how to carry out each of the circled tasks in Figure 3 and to appreciate why this approach is better, in terms of improved software development and just as importantly, in terms of the increased longevity of  your software skills.

      Some of the concepts to be developed are associated with the specification, implementation and test plan tasks, as follows:

      ·         formulate requirements:

      à         actors

      à         interfaces

      à         use cases

      ·         analyze:

      à         objects

      à         classes

      à         interactions

      ·         specify behavior:

      à         states and transitions

      à         constructors, queries, commands

      à         collaborations

      à         message exchanges

      ·         implement:

      à         inheritance

      à         hierarchical construction

      à         class reuse

      ·         test plan:

      à         test cases from use cases/behavior

      à         coverage

      à         efficiency

      à          reuse

      These concepts merge  two steams of ideas. Object orientation provides an operational level tool kit that supports effective software development. However, the framework that provides the guiding light to achieve such effectiveness is that of systems theory -- specifically, its concepts of state and behavior, and of hierarchical system construction.

      Chapter 2 Coordination in Team-based Software Development: Role of the Blueprint

      Team Work: The Need for Coordination

      Why organization is is needed and how does it relate to the progress that a group of individuals can make in developing software?  If writing software were like picking cotton, very little organization would be needed and essentially the more workers there are the more work gets done. However, in software development coordination is essential and as a consequence adding more workers to a project may be counterproductive. How so?

       Some insight can be derived from a model that is derived from the concept of speedup in multi-processor computing systems where processing work is distributed among many computers.  Whether distributing software development tasks among individuals or executable code among processors, it is well known that more is not necessarily better.  If one person/processor can do a job in one day, it may not happen that two people/processors can do the job in half the time, nor three people/processors in one-third, and so on.  One model for why this is true separates the tasks performed by individuals into

      Enjoying the preview?
      Page 1 of 1