Data Flow Diagrams Rules and Software Cost Estimation: Case Study and Examples – MCS-14

Shared by SteadyAtlas9417 October 28, 2026 PDF
Computer Science Information Systems MCS-14 8 pages $8
Page 1 shows the heading 'DOTCOM / MCS-14 / 207' and a case study question on drawing an Entity Relationship Diagram for a Railway Reservation System.
Page 1 · free preview
Page 2
Page 3
Page 4
Page 5
Page 6

Unlock all 8 pages

Get it free by sharing your own notes, buy just this one, or become a member and unlock documents with your plan.

How to unlock this document

Choose the way that suits you. Each one gives you all 8 pages to read online and the PDF to download.

Free

Share your notes, unlock for free

2 free unlocks for every 5 approved uploads

  • Upload your own lecture notes, assignments, essays or past papers
  • PDF, Word, PowerPoint and Excel files all work, and you can send many at once
  • We check each upload; you get a notification when it is approved
  • Spend a free unlock on this document or any other, and keep it for good
  • Shared under your public username, never your email
Create a free account

Then upload your notes from your profile.

Just this one

Buy this document

$8 one-time payment

  • All 8 pages of this document, yours to keep
  • Download the PDF and read it any time, also offline
  • No subscription and nothing to cancel
  • Find it again any time under My Profile → Library

You log in or create a free account first, then pay securely.

Best value

Become a member

Unlock documents from the whole library, which keeps growing

  • Choose any documents you like, up to your plan’s unlocks
  • Documents you unlock stay yours, even if you cancel later
  • Your unlocks start again with every renewal
  • Secure checkout by Dodo Payments
10 tokens every month
60 tokens every 6 months · Save 17%
130 tokens every year · Best value

You log in or create a free account first, then pay securely.

Compare the plans

About this document

Pages
8 pages
Price
$8 one-time, yours to keep
Membership
Included in every plan
Format
PDF
Subject
Computer Science, Information Systems
Module
MCS-14

This document covers rules for drawing Data Flow Diagrams (DFDs) and provides examples for a Student Information System. It also discusses software cost estimation techniques, including the Constructive Cost Model (COCOMO).

What's inside

  • Rules for drawing Data Flow Diagrams
  • Entity Relationship Diagram for a Railway Reservation System
  • Entity Relationship Diagram for a Student Information System
  • Software cost estimation techniques
  • Constructive Cost Model (COCOMO)
  • Intermediate COCOMO and cost drivers

Who it is for: Students taking a course on Data Flow Diagrams, likely in Computer Science or Information Systems. (Undergraduate)

#case study #cocomo #data flow diagrams #dfd #mcs-14 #software cost estimation #software project #student information system

Share with classmates: WhatsApp Telegram X LinkedIn Facebook

Summary

Data Flow Diagrams are tools for visualising how data moves through a system. Software cost estimation is a method for predicting the effort and time needed to develop software. Students get examples of Data Flow Diagrams and Entity Relationship Diagrams. They also learn about the COCOMO model for software cost estimation.

Data Flow Diagrams

Data Flow Diagrams show how data moves through a system. Rules for drawing them include ensuring each process has data flows in and out. Students draw Data Flow Diagrams for a Student Information System.

Entity Relationship Diagrams

Entity Relationship Diagrams show how data is stored and related. Students draw Entity Relationship Diagrams for a Railway Reservation System and a Student Information System. They make necessary assumptions.

Software Cost Estimation

The COCOMO model estimates software development effort and time. It uses program size and cost drivers to calculate effort applied and development time. Students learn about Basic, Intermediate and Detailed COCOMO.

Software Testing

Software testing methods include black box testing and white box testing. Black box testing treats the software as a black box, without knowledge of internal implementation. White box testing uses internal data structures and algorithms.

Key terms

Data Flow Diagram
A diagram that shows how data moves through a system.
Entity Relationship Diagram
A diagram that shows how data is stored and related.
COCOMO
A hierarchy of software cost estimation models.
Black box testing
A testing method that treats the software as a black box.
White box testing
A testing method that uses internal data structures and algorithms.
Cost drivers
Subjective assessments of product, hardware, personnel and project attributes.

Questions this document helps with

  • How do you draw a Data Flow Diagram?
  • What are the rules for drawing Data Flow Diagrams?
  • What is the COCOMO model for software cost estimation?

Summary written with AI from the document's text.

Ask the AI Teacher

Ask any question about this document or your course, and get a clear explanation.

Free accounts can ask 5 questions a day.