written 8.7 years ago by |
Software Architectures - Jun 2014
Computer Science Engg. (Semester 8)
TOTAL MARKS: 100
TOTAL TIME: 3 HOURS
(1) Question 1 is compulsory.
(2) Attempt any four from the remaining questions.
(3) Assume data wherever required.
(4) Figures to the right indicate full marks.
1 (a) With the help of next block diagram of ABC (architecture business cycle). Explain in detail the different activities which are involved in creating a software architecture.(10 marks)
1 (b) Enumerate and explain in detail, the different groups of software architectures structure are categorized into, with the help of appropriate pictorial description.(10 marks)
2 (a) Explain in brief about KWIC (keyboard in context) with shared data solution.(10 marks)
2 (b) Explain in brief about pipes and filters style, with diagram.(10 marks)
3 (a) Explain what is availability? Explain general scenario for availability?(10 marks)
3 (b) What do you mean by tactics? Explain availability tactics with neat diagram.(10 marks)
4 (a) What do you mean by architectural pattern? How it is categorized? Explain the structure part of the solution for ISO layered architecture.(10 marks)
4 (b) Define blackboard architectural pattern? Briefly explain steps used to implement the black board pattern.(10 marks)
5 (a) What do you mean by broker architecture? What are the steps involved in implementing distributed broker architecture patterns?(10 marks)
5 (b) Explain with neat diagram, the dynamic scenarios of model view controller (MVC).(10 marks)
6 (a) What are the steps involved in implementing the microkernel system?(12 marks)
6 (b) What are the benefits and liabilities of 'Reflection architecture'. Patterns?(8 marks)
7 (a) Discuss the five steps implementation of Master-slave-pattern.(10 marks)
7 (b) Explain in brief about variants of whole-part-design pattern, in brief.(10 marks)
8 (a) Brief explain the different steps performed while designing an architecture using the ADD method.(10 marks)
8 (b) (i) Forming team structures.(5 marks)
8 (b) (ii) Documenting across views(5 marks)
8 (b) (iii) Documenting interfaces.(10 marks)