• To explain the role and importance of modelling in software requirements, architecture and design activities
  • To demonstrate the practical application of several modelling languages
  • To derive complete detailed design from requirements specification
  • To design a creative process to manage the complexity of software system



  • Ability to translate a specification into a design

  • Familiarize with standard UML notations and understand how to model requirements with Use Cases


Unit – I

Software Engineering- Paradigms - Planning - Cost estimation - Software project scheduling - Risk analysis and management - Requirements and specifications - Stakeholders needs and analysis.


Unit – II

Structured Design- Design principles - Problem partitioning and hierarchy - Modularity - Top-down and bottom-up strategies - Transformation of a DFD to a structure chart - Coupling and cohesion.


Unit – III

Object-oriented analysis- UML - Use case - Conceptual model - Class analysis patterns - Overview - Diagrams - Aggregation - Collaboration - Sequence - Class - Managing analysis and design.


Unit – IV

Architecture Concepts- Design methods - Design patterns - Design processes and strategies - Design by template incremental design.


Unit – V

Structured systems analysis and structured design - JSP - JSD.



  1. David Budgen, "Software Design", Second Edition, Pearson Education, 2004.
  2. R. S. Pressman, "Software Engineering", Fifth Edition, McGraw Hill Inc., 2001.



  • E. D. Downs, Peter Clare, and Jan Coe, "Structured System Analysis and Design Methods - Application & Context", Prentice Hall, 1998