Large scale Software development

Large scale Software development

1. Leaning outcomes of the model:

   • 1. Essentital characterisitics of larage scale software systems development
     • 2. Development processes for larage scale systems - including agile
       • 3. Frameworks for enterprise systems
         • 4. Applying frameworks
           • 5. concepts of compnents, interfaces, services
             • 6. Artchitecture
               • 7. Cloud Computing

2. What ate the challenges for software development now and in the future?

   • Maintaining old software
     • Internet of things, everything is on the internet
       • Requirements for software keep on changing
         • System will get complex
           • Time zone
             • Multi languages
               • How do you test software round the world
                 • How do you know you have done it correctly? How would you ask a million users
                   • Releasing the software on the market
                 • user ability
                 • statistics
     • With all the different languages available and the new updates, with the differences it may be difficult switching to a new language

3. Agile processes - how would they apply to large scale system

   • Break up the system, smaller teams can look at different parts of the system.

4. How do you manage complexity

5. Does scale and complexity go hand in hand?

   • Yes. The two go hand in hand, however depends on the application. Simple application for billion users still means complex procedure.
   • An example of this is systems of systems. Examples include games technology, personal email and healthcare. Internet of things.

6. virtualization

   • Back in the day you would buy all hardware yourself and you would own everything, you’d control everything. Now you just re-use a service not caring where it is etc. This results in decreased role of localised data and processing.
     • Economic Option for development
       • DIY (do it yourself)
         • - keep it in-house, recruit skilled engineers
           • - Flexible, controllable development, but re-inventing the wheel? Risks of development?
       • Buy complete package
         • - Get somebody else to do it
           • - Tents to be a generic product, rather then customised to specific needs to requirements
             • - More costly, but better quality?

7. what are we going to see more off?

   • systems becoming independent, AI

8. Building large system

   • Most of the time you have code that can be reused from developers.

9. Acquiring Components and Services

   • cost of acquisition - in terms of investment. Need to consider full lifetime costs i.e. both development / purchase costs and maintenance / license cost
   • Integration and interoperability - with existing system capabilities and technical platform
   • Managing risk of acquisition:
     • Control over development
       • Functional complexity and performance of components or services