Latest Activity In Study Groups

Join Your Study Groups

VU Past Papers, MCQs and More

We non-commercial site working hard since 2009 to facilitate learning Read More. We can't keep up without your support. Donate.


Assignment No. 02
Semester Spring 2015
Software Engineering I – CS504
Graded Assignment
Total Marks: 15
Due Date: 10-06-2015
Objectives The objective of this assignment is:

• To assess your overall understanding of Software Engineering concepts.

• To increase your level of understanding about requirement engineering phase.

• To help you understand how to effectively collect requirements.
Note
This Assignment is a Graded Assignment.
The assignment should be in .doc format. Assignment in any format other than MS Word format will not be accepted.
Assignment submitted through email will not be accepted.
This assignment is covering Software Requirements Engineering Lectures 10-16.
Recall the lectures delivered for Software Requirements engineering and solve your assignment
For any query about the assignment, contact at cs504@vu.edu.pk


Project Description:
A Brief Case Study of Coca Cola’s Company: The Coca-Cola Company is the world's leading manufacturer, marketer, and distributor of nonalcoholic beverages. The ultimate objectives of their business strategy are to increase volume, expand their share worldwide, maximize long-term cash flows and create economic value.
A brief introduction of Coca Cola’s Management Accounting Information System is that it is controlled by its accounting managers. Management accounting is related to accounting information adopted by companies for internal decisions made on how the business should be operated in terms of expenses sustained and sales generated from such expenses. Coca-Cola makes use of cash book ledger for its management accounting information and the company’s cash book ledger is divided into two sections. One section is used for cash disbursement journal record of all the payments made such as accounts payable and operation expenditures. The second section contains the cash journal that contains all cash record and receipts such as cash sales and accounts receivable. Company keeps record of all these journals on daily bases with respect to any given transaction performed.


Q#1. By considering the case study, draw the UML object model diagram by extracting entities and functions hidden in the case study of Coca Cola’s Management Accounting Information System. ( 10 Marks )


Q#2. Derive five non-functional requirements of Coca Cola’s Management Accounting Information System. ( 5 Marks )


Note: Assignment should be in your own words and not copied from internet, handouts or books. 
Your answer should be “to the point”. We wish you very best of luck for your Assignment. The deadline for Assignment no 1 submission of the course CS504 is Wednesday 10th June-2015.

 

Views: 12253

Attachments:

Replies to This Discussion

koi diagram nai share kr rha different.sb wahi aik sy kam chala rhy :(

Question # 2                                                                                                             5 Marks=========================================================================

Derive five non-functional requirements of Coca Cola’s Management Accounting Information System?

 

Answer:-

 

Non-functional requirements are the constraints or restrictions under which the developed system (Software) must operate. Non-functional requirements are also known as quality attributes.

Non-functional requirements of Coca Cola’s Management Accounting Information system are as follows:

 

The Management Accounting System must be user friendly. (Each user having little knowledge can use it easily.)

 

The system must be able to perform all the operations precisely and accurately with fast speed.

 

The developed applications must be able to perform all on-going operations without any error or problem.

 

 

This application must provide security of accurate results to all the users. The accounting system must protect accounting information from unauthorized access (read and write). The accounting system communication channels must be secure (they will support confidentiality and data integrity).

Developed system must allow maintainability (changes or any modifications).The accounting system will support automatic and manual updates.The system should reduce as much as possible system administrator work.

CS504MC140202815

Attachments:

1      Non-Functional Requirements

1.1      Security

Req-15.0

The accounting system must protect accounting information from unauthorized access (read and write)

Explanation

Accounting information contains detailed information about users and systems.  Typically, sites want to keep this information private to prevent cyber security incidents and to respect the privacy rights.

 

Req-15.1

The accounting system communication channels must be secure (they will support confidentiality and data integrity)

Explanation

See explanation of req-15.0.

In addition, international agreements require that user’s accounting data must be encrypted when crossing national borders.

1.2      Interoperability

Req-16.0

The accounting system must interoperate with TeraGrid and LCG (EGEE and gLITE).

Explanation

Many VOs will use multiple grids from the OSG partners. The accounting systems of the difference grids must be able to exchange data so that reports about resource consumptions at the VOs can be compiled.

1.3      Scalability

 

Req-17.0

The accounting system must be able to track at least 1,000 services instances.

Explanation

Currently deployed grids have no more than 100 services running.

 

Req-17.1

An accounting system repository must support up to 10,000 users or querying accounting information concurrently.

Explanation

None.

1.4      Fault Tolerance

 

Req-18.0

The accounting system must monitor its components and communication channels

Explanation

Because the accounting information will be used to evaluate VO-resource providers contracts and resource allocation models, it is paramount that users have a certain confidence in the produced accounting information. Lack of accounting information due to an internal failure must be distinguished from the lack of accounting information due to a service inactivity or failure.

 

Req-18.1

The accounting system must be structured so that a it is possible to build a system that does not have a single point of failure

Explanation

As a complete (hardware+software) the accounting system should be deployable in such a way that the system would not have a single point of failure.

1.5      Flexibility and Extendibility

Req-19.0

The accounting system must be flexible and extendible so that the introduction of a requirement to support a specific economic model does not require major redesign or radical changes in the architecture.

Explanation

Even though the first version of the accounting system is concerned only with tracking the usage of services and resources, it is very likely that in the future an economic model for resource allocation will emerge and be adopted by the OSG.

1.6      Maintainability

 

Req-20.0

The accounting system will support automatic and manual updates.

Explanation

The system should reduce as much as possible system administrator work.

Supply Chain Function

It’s ensuring customers everywhere stay refreshed. Operating a global business places tremendous demands on the supply chain. That’s why at The  Company, you’ll find the very best people answering the call everywhere we do business.

We ensure that every link in the chain stretching from bottler to consumer is working together. We cover every aspect of supply from Procurement and Manufacturing (including Quality, Environment, Safety & Health), to Engineering and Logistics.

Question no 1

Question#2

Derive five non-functional requirements of Coca Cola’s Management Accounting Information System?

Answer:

Non-functional requirements are the constraints or restrictions under which the developed system (Software) must operate. Non-functional requirements are also known as quality attributes

Non-functional requirements of Coca Cola’s Management Accounting Information system are as follows

1. Usability:

The application must be user friendly. (Each user having little knowledge can use it easily)

2. Performance:

The system must be able to perform all the operations precisely and accurately with fast speed

3. Reliability:

The developed applications must be able to perform all on-going operations without any error or problem.

4. Security:

This application must provide security of accurate results to all the users.

5. Maintainability

Developed system must allow maintainability (changes or any modifications)

 More requirements can be added according to understanding.

RSS

© 2021   Created by + M.Tariq Malik.   Powered by

Promote Us  |  Report an Issue  |  Privacy Policy  |  Terms of Service