Problem Description (6 points Article Systems (AS), a giant books franchise has

Question

Problem Description (6 points Article Systems (AS), a giant books franchise has approached IT company ABCLtd. To shift them online so all of its outlets across the processes and help them automate their business globe would be under one portal. AMC Ltd, agrees to take on the project and both the companies sit down and strike a deal. After detailed discussion and analysis, ABC Ltd. decides to follows the waterfall model for development of the project. This discussion covered topics such as the business analysis and operations of AS. The expectations of the client (AS) from ABC Ltd their needs and requirements from the software, their current existing system including its limitations and what the proposed system would do to address these issues. Taking into account all the input, the concerned team at ABC designed and developed the SRS Which of the following are typically expected to be found in the SRS created by ABC Ltd Towards the AS Project? Put an X mark in the second column of Table 2 for those SRS elements that will be included in the SRS document then explain why you have selected these elements in table 3 Table 2 Elements in software Requirements Specification document To be included System Overview Class Diagram Source Code Use Cases Flow Charts for algorithms realizing the functionality of the system Code review Comments test results The Difference in the scope of the current system to be Non-Functional requirements Features of new portal to be devel ed system. Table 3 r explanation inside this box

Explanation / Answer

1)System Overview :

System overview is most importent phase in SRS document,It gives the user viewpoint of product.It's talks about entire infrastructure including characteristics of the users of this project, the product's hardware, and the functional and data requirements of the product and helps in defining the overall system architecture.The functional requirements, data requirements and constraints and assumptions made while designing the Application.

Indentified the following in the Document:

• System Requirements:

• Language, Operating System, Platform

• Performance/Reliability Requirements:

• Constraints

• Quality Ranges

• Product overview including assumptions and dependencies

2)Class Diagrams :

Class diagrams are a type of structure diagram because they describe what must be present in the system being modeled. It separates the design elements from the coding of the system. Since classes are the building block of objects, class diagrams are the building blocks of UML. The diagramming components in a class diagram can represent the classes that will actually be programmed, the main objects, or the interaction between class and object.

I do understand certain function that is in one particular diagram must be reflected in specific diagram to ensure consistency so based on our requirement.

Its very easy to understand the system and develop the application further.

3)Source Code : Should not include source code into SRS document hence SRS talks about only requirment specification.

4)Use Cases :

In Use case section useful to understand the dependence between each compent of architecture.

Fallowing descriptions need to provide in usecase section:

Actor Descriptions
Provide completely defined entries for all of the actors in the use case diagram.

Use Case Descriptions
Provide completely defined entries for all of the use cases in the use case diagram.

Class Descriptions
Provide partially defined entries for all the classes in the class diagram. The fields for the name, description, attributes, and relationships must be completed on the data dictionary form of each class in the class diagram for the SRS document.

5) Flowchars for algorithams realizing the functionality of the system: Its not part of SRS document so we can exclude from SRS document

6)Code Review Comments :Its not part of SRS document so we can exclude from SRS document.

7)Test Results : Its not part of SRS document so we can exclude from SRS document

8)The difference in the scope of the current system to be proposed system:

This section most importenant for further enchancement and project sucess, Specify the exact project scope indicating project boundaries. This can also include the purpose of the software project, its benefits and overall goals. In the case of a software product, this should contain product vision and should indicate the exact user base for the product. If you are aware of features that should go into a future version, list them here or add a new section on “Features for Future Releases"

9)Non-Functional Requirements :

Performance : It describes,What is the response time required?
Scalability : It describes,how many users the system should support after two years of operation?
Security : It describes,is data encryption required?
Maintainability : It can be easy to modified to correct faults.
Usability : It describes how the user can easily operate the application
Multi lingual Support : It describes,What are the languages that software system should support?
Auditing and Logging : It describes, How many users logged and what is best time to use the application ..etc
Availability : It describes,Is any kind of downtime acceptable or required?

10) Features of new portal to be developed: Its not past of current SRS document hence its going to developed as new application.

Related Questions

Navigate

• Browse (All)
• Browse P
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.