General discussion

  • Creator
    Topic
  • #2092607

    Object Orientation Implementation

    Locked

    by pdsmith ·

    We have a Methodology at my company and I have been working on the implementation phase of that. The Methodology is currently set up for a structured style development. As our company moves toward object orienated development, we need to make somechanges to the Methodology. Does anyone have any suggestions for how the implementation phase could be affected by object orienated design?

All Comments

  • Author
    Replies
    • #3868742

      Object Orientation Implementation

      by realgem ·

      In reply to Object Orientation Implementation

      I’m not sure what you mean by implementation. Does it include requirements, design. Or is this a RAD methodology, or what?

      From your last sentence, it looks as if you are strictly worried about the coding that comes after the design.

      I thinkthat you should consider more frequent “builds” during implementation. This is due to the height of the object tree. Traditional development is “flatter” and so integration is not as complex. My experience is that smaller, incremental builds and tests is very much easier to manage.

      You should also include steps to identify opportunities for re-use of existing objects. Some of this is part of design, but it must continue throughout implementation. To keep things as neat and tidy as possible, you should consider having “reuse reviews”, where the programmers get to offer suggestions to their peers.

      Your testing processes will change due to the potential for widespread impact when high-level objects are changed. Many instances willhave to be tested. Make more allowance for testing.

      Implementation must also allow for updates to object libraries, etc.

    • #3882777

      Object Orientation Implementation

      by wayne m. ·

      In reply to Object Orientation Implementation

      From a project management stand point, there will probably be no changes for an object oriented style, except for additional learning curve time for the developers during the first couple of projects.

      Developing object oriented code is different than procedural code and the shift is more difficult for some developers than others. Trade offs between too few and too many classes and too little and too much hierarchy are subjective at best and primarily based on experience. A good mentor withan easy going personality would be very helpful. See if you have one in house or can contract or hire one.

      Add at least 2 months to the first 6 months of the project schedule for your first OO development. In the long run, OO will reduce development schedules and improve quality, but for the first couple of tries, there will be learning curve, so pick your projects appropriately.

      • #3882064

        Object Orientation Implementation

        by wayne m. ·

        In reply to Object Orientation Implementation

        P.S. Ignore software resuse at this stage. Trying to design for reuse when introducing OO design will just cause your developers to lose focus. There is enough learning curve in the process already, so don’t add to it.

      • #3881860

        Object Orientation Implementation

        by pdsmith ·

        In reply to Object Orientation Implementation

        This is what I was thinking, I appreciate your help.

    • #3881858

      Object Orientation Implementation

      by pdsmith ·

      In reply to Object Orientation Implementation

      This question was closed by the author

Viewing 2 reply threads