
- •11. Why do we need documentation?
- •12. What is Subversion?
- •13. What is dd? Why do we need it?
- •14. What is Use-Case? Why do we need it?
- •15.(Context: Design patterns) Describe Builder pattern. Give an example
- •16. The importance of software design can be summarized in a single word. What is it? Explain
- •17. Why each requirement has to be specified in detail?
- •5 Major Steps in Requirements
- •18. (Context: Design concepts) Explain Information hiding
- •19. What is ftr? Why do we need it?
- •20. What is coupling?
- •21. In terms of design, what is interface?
- •11. What is the real test of a good requirements document?
- •12.(Context: Source control) Describe branching/merging/ tagging.
- •13. What is srs? Why do we need it?
- •14. What is Feature? Why do we need it?
- •15. (Context: Design patterns) Describe Singleton pattern. Give an example
- •16. What are the characteristics of a good design?
- •17. What are some of the responsibilities of project manager?
- •18. (Context: Design concepts) Explain Refactoring
- •19. Furps should be a target for all software. What is it?
- •20. Describe the three main barriers faced during the elicitation of requirements
- •21. What is cohesion?
13. What is srs? Why do we need it?
SRS (Software Requirements Specifications)
SRS IS SOFTWARE REQUIREMENT SPECIFICATION DOCUMENT,WHICH
CONTAINS ALL THE INFORMATION REGARDING THE SYSTEM.IT
CONTAINS TECHNICAL AS WELL AS NON TECHNICAL
INFORMMATION.AFTER THE FEASIBILTY STUDY AN SRS IS PREPARED
BY A TEAM WHICH CONATAINS SYSTEM ANALYST,PROJECT
MANAGER,TEST LEAD AND CLIENT.
A software requirements specification (SRS) – a requirements specification for a software system – is a complete description of the behavior of a system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. In addition to use cases, the SRS also contains non-functional requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints).
14. What is Feature? Why do we need it?
Feature (software design) is an intentional distinguishing characteristic of a software item (in performance, portability, or - especially - functionality). A system is said to be feature-rich when it has many options and functional capabilities available to the user. Progressive disclosure is a technique applied to reduce the potential confusion caused by displaying a wealth of features at once.
15. (Context: Design patterns) Describe Singleton pattern. Give an example
The singleton pattern is one of the simplest design patterns: it involves only one class which is responsible to instantiate itself, to make sure it creates not more than one instance; in the same time it provides a global point of access to that instance. In this case the same instance can be used from everywhere, being impossible to invoke directly the constructor each time.
16. What are the characteristics of a good design?
Recognizable architectural styles or patterns; components with good design characteristics; thereby facilitating implementation and testing
Modularity
Distinctness
Independence of functional characteristics
Little complexity of connections
17. What are some of the responsibilities of project manager?
Project management consists of managing the production of a product within given time and funding limits. Since this requires human resources, project management involves not only technical and organizational skills, but also the art of managing people. Project management involves the planning, monitoring, and control of the people, process and events that occur as software evolves from preliminary concept to operational implementationPlanning, monitoring and control of
People
Process
Events
as software evolves from preliminary concept to operational implementation
Management activities
Proposal writing.
Project planning and scheduling.
Project costing.
Project monitoring and reviews.
Personnel selection and evaluation.
Report writing and presentations.
Why is it important?
As we have just seen, many projects fail
Building software is a complex task – particularly if it involves a lot of people and takes place over a long period of time
What are the steps?
Understand the four P’s:
People – must be organised to work effectively
Product – must have effective communication with the customer to specify scope and requirements
Process – must be appropriate for people and product
Project – must estimate effort & time needed, define work products, establish quality checkpoints, establish methods to monitor & control work defined by plan
We will focus on people and project