This document provides instructions for students to complete practical projects related to project management. It outlines 4 practical assignments:
1. Create a System Requirement Study (SRS) for a sample inventory management project using UML diagrams.
2. Use the waterfall model to prepare a flow chart and Gantt chart for a student project.
3. Estimate the cost of a project using Function Point Analysis (FPA), which involves counting types of system functions and weighing them based on complexity.
4. Estimate the cost of a project using the COCOMO model, which is a regression model that uses parameters from historical data and current project characteristics in a basic formula.
The document discusses SAP's preventive maintenance and condition-based maintenance capabilities. It covers the core functions of setting up preventive maintenance plans based on time, performance, or condition. It also discusses using "light" condition-based maintenance capabilities in SAP to monitor asset health parameters and trigger maintenance workflows. Finally, it presents SAP's rapid deployment solution for condition-based maintenance which provides asset health dashboards, manual/automatic triggering of maintenance from sensor data, and integration with SAP EAM.
The document discusses implementing an ERP management system for a real estate company called Nirmala Consol Private Limited. Currently, the company's bill generation process takes 3 months to complete. Implementing an ERP system would integrate different departments like marketing, finance, IT, and HR. It would allow efficient data sharing and minimize the bill generation process to only 4 days. An ERP system would improve information quality, decision making, planning, cash management, inventory management, productivity and other operational functions. It would reduce the time management accountants spend on data collection and increase the time spent on analysis. In conclusion, an ERP system offers long term cost efficiencies and enhances communication and productivity across the organization.
The document discusses function points as a standardized way to measure software productivity and size. It argues that software companies should know how much software they produce through formal measurement programs. Function points count the number of inputs, outputs, inquiries and files to objectively measure the size of software and allow for accurate estimation of costs, schedules and productivity. While challenging to implement, formal software measurement programs using function points provide many benefits for software organizations.
Early Function Point Analysis and Consistent Cost Estimating (2015-04-30) - A...Nesma
Early Function Point Analysis and Consistent Cost Estimating. "You cannot apply FPA in early stages of the software development process, so the practice of budgeting software development Function Point Analysis (FPA) is useless."
"You need a high level of detail of the software requirements before you can successfully apply FPA."
"Cost estimating and budgeting early in the software development lifecycle using FPA takes lots of time and is inaccurate. It’s not worth the effort".
No! No! No! These are widespread misunderstandings, that prevent people to benefit from FPA at virtually any moment!
Adri Timp’s presentation shows how to apply FPA in early stages of development or enhancement and how to maintain a consistent size and cost estimation approach throughout the software development lifecycle:
- Estimating the functional size of a development or enhancement project, if not all of the details of the software
requirements are known;
- Estimating the functional size if all the details of the software requirements are known, but it is required to significantly speed up the FPA process, using default values for complexity;
- Estimating the functional size, if only the data functions are known;
- Dealing with autonomous growth: autonomous growth occurs through revealing functionality while detailing the
specifications and this functionality was not originally counted;
- Dealing with scope creep: scope creep leads to new functionality which would not have been found even with more detailed specifications;
- How to maintain a consistent size and cost estimation approach throughout the software development lifecycle.
The Functional Sizing Standards Committee (FFSC) of IFPUG will release a uTip guide about this subject later in the year.
The document describes 7 case studies that illustrate different configurations of the eMaint X3 CMMS system for various customer needs. The case studies cover configurations for calculating job times and downtimes, response times and metrics reporting, equipment availability tracking, call center and room management, and use of the planner and timecard tools.
Introduction to function point analysis v1.0Gunesh Apte
This small course covers basic concepts of Function Point Analysis, and Software Non-Functional Assessment process.
It explains the importance of using Function Point Analysis in simple & lucid language.
It explains some practical software project scenarios, where Function Points and SNAP can be applied.
At the end, it discusses benefits of using Function Points for IT organizations.
The document discusses SAP's preventive maintenance and condition-based maintenance capabilities. It covers the core functions of setting up preventive maintenance plans based on time, performance, or condition. It also discusses using "light" condition-based maintenance capabilities in SAP to monitor asset health parameters and trigger maintenance workflows. Finally, it presents SAP's rapid deployment solution for condition-based maintenance which provides asset health dashboards, manual/automatic triggering of maintenance from sensor data, and integration with SAP EAM.
The document discusses implementing an ERP management system for a real estate company called Nirmala Consol Private Limited. Currently, the company's bill generation process takes 3 months to complete. Implementing an ERP system would integrate different departments like marketing, finance, IT, and HR. It would allow efficient data sharing and minimize the bill generation process to only 4 days. An ERP system would improve information quality, decision making, planning, cash management, inventory management, productivity and other operational functions. It would reduce the time management accountants spend on data collection and increase the time spent on analysis. In conclusion, an ERP system offers long term cost efficiencies and enhances communication and productivity across the organization.
The document discusses function points as a standardized way to measure software productivity and size. It argues that software companies should know how much software they produce through formal measurement programs. Function points count the number of inputs, outputs, inquiries and files to objectively measure the size of software and allow for accurate estimation of costs, schedules and productivity. While challenging to implement, formal software measurement programs using function points provide many benefits for software organizations.
Early Function Point Analysis and Consistent Cost Estimating (2015-04-30) - A...Nesma
Early Function Point Analysis and Consistent Cost Estimating. "You cannot apply FPA in early stages of the software development process, so the practice of budgeting software development Function Point Analysis (FPA) is useless."
"You need a high level of detail of the software requirements before you can successfully apply FPA."
"Cost estimating and budgeting early in the software development lifecycle using FPA takes lots of time and is inaccurate. It’s not worth the effort".
No! No! No! These are widespread misunderstandings, that prevent people to benefit from FPA at virtually any moment!
Adri Timp’s presentation shows how to apply FPA in early stages of development or enhancement and how to maintain a consistent size and cost estimation approach throughout the software development lifecycle:
- Estimating the functional size of a development or enhancement project, if not all of the details of the software
requirements are known;
- Estimating the functional size if all the details of the software requirements are known, but it is required to significantly speed up the FPA process, using default values for complexity;
- Estimating the functional size, if only the data functions are known;
- Dealing with autonomous growth: autonomous growth occurs through revealing functionality while detailing the
specifications and this functionality was not originally counted;
- Dealing with scope creep: scope creep leads to new functionality which would not have been found even with more detailed specifications;
- How to maintain a consistent size and cost estimation approach throughout the software development lifecycle.
The Functional Sizing Standards Committee (FFSC) of IFPUG will release a uTip guide about this subject later in the year.
The document describes 7 case studies that illustrate different configurations of the eMaint X3 CMMS system for various customer needs. The case studies cover configurations for calculating job times and downtimes, response times and metrics reporting, equipment availability tracking, call center and room management, and use of the planner and timecard tools.
Introduction to function point analysis v1.0Gunesh Apte
This small course covers basic concepts of Function Point Analysis, and Software Non-Functional Assessment process.
It explains the importance of using Function Point Analysis in simple & lucid language.
It explains some practical software project scenarios, where Function Points and SNAP can be applied.
At the end, it discusses benefits of using Function Points for IT organizations.
The document discusses the benefits of SAP's Plant Maintenance (PM) module. The PM module allows companies to: 1) plan and manage preventative maintenance to reduce breakdowns and increase equipment availability; 2) identify and rectify equipment problems whether from failure or deterioration; and 3) break maintenance down into different levels for both planning and performing tasks at either the individual equipment or functional location level. Overall, the PM module standardizes maintenance practices, integrates maintenance with other business functions, and provides structured cost and equipment history data for better resource control and cost management.
The document discusses software configuration management (SCM). It defines SCM as identifying, organizing, and controlling modifications to software being built by a programming team, with the goal of maximizing productivity by minimizing mistakes. SCM involves activities to identify, control, and track changes throughout the software development process. An important part of SCM is the repository, which stores software configuration items and allows developers to manage changes effectively.
Solution Manager - SAP NW BW on HANA Setup Part 3 of 3 (Technical Monitoring ...Linh Nguyen
This document provides instructions for configuring technical monitoring in SAP Solution Manager, including defining the monitoring scope, assigning monitoring templates to managed systems, specifying which metrics will be collected, and checking the monitoring configuration and sample alerts. It emphasizes that setting up Solution Manager monitoring is a multi-step project involving preparing the infrastructure, configuring managed systems, and defining the monitoring scope and reporting.
This document provides an overview of the general store inventory system design project. It includes sections that describe the context diagram, data flow diagrams, entity relationship diagram, class diagram, activity diagram, sequence diagrams, and architecture design. The document also lists the various forms and reports that will be used in the system, such as products, customers, suppliers, transactions, sales, and stock management.
KMR Soft Online Training offers extensive training of corporate employees. KMR Soft team specialize in strive applied solutions and learning platforms ideal to increase your quiescent reach, within the organization to enhance the arena performance. We work out constituent that acquaintance techniques with asynchronous teamwork that helps the organization training techniques more efficiently.
Keynote talk by Marlon Dumas at the Bolzano Rules and Artificial INtelligence Summit (BRAIN 2019), RuleML+RR and GCAI Conferences, Bolzano, Italy, 17 September 2019. The talk gives an overview of state-of-the-art methods in the field of process mining and predictive process monitoring and spells out research challenges in the fields of prescriptive process monitoring and automated process improvement.
This document discusses Function Point Analysis, which is a technique for measuring the size of software systems. It breaks systems into smaller components like external inputs, outputs, inquiries, internal logical files, and external interface files. Counting these components provides a total Function Point that can be used to measure a system's size, track scope changes, and compare productivity across tools and languages. The benefits are that Function Points allow for accurate sizing, can be counted consistently, and help with estimating and communicating a system's size to stakeholders.
The document discusses key aspects of requirements engineering including types of requirements, the requirements engineering process, and techniques used in requirements elicitation and analysis. It describes user requirements, system requirements, functional requirements, non-functional requirements, and domain requirements. The requirements engineering process involves activities like feasibility studies, requirements elicitation and analysis, requirements specification, validation, and management. Requirements elicitation and analysis techniques include requirements discovery, classification, prioritization, documentation, and dealing with issues that can arise.
Function point analysis is a method of estimating the size of a software application based on the user view rather than lines of code. It involves identifying and classifying functional components such as internal logical files, external interface files, inputs, outputs, and inquiries. Each component is assigned a complexity and weight to calculate the total functional size in function points. The size can then be adjusted based on 14 general system characteristics to determine the final adjusted size. The document provides details on the history, vocabulary, types of data and transactions, counting process, and complexity determination involved in function point analysis.
Using Function Point Metrics For Software Economic StudiesCAST
The document discusses the use of function point metrics for software economic studies. It notes that function points are well-suited for productivity analysis as they avoid distortions from lines of code metrics. Function points support various types of analyses including cost, quality, and value studies. The document outlines the evolution and expansion of function point uses from 2010 to 2020, including new domains like delivery, quality, and portfolio analysis. It emphasizes the need to extend function point counting to smaller and larger projects.
Robust configuration management (CM) practices are essential for creating continuous builds to support agile’s integration and testing demands, and for rapidly packaging, releasing, and deploying applications into production. Classic CM—identifying system components, controlling change, reporting the system’s configuration, and auditing—won’t do the trick anymore. Bob Aiello presents an in-depth tour of a more robust and powerful approach to CM consisting of six key functions: source code management, build engineering, environment management, change management and control, release management, and deployment. Bob describes current and emerging CM trends—support for agile development, cloud computing, and mobile apps development—and reviews the industry standards and frameworks essential in CM today. Take back an integrated approach to establish proper IT governance and compliance using the latest CM practices while offering development teams the most effective CM practices available today.
The document discusses workflow and provides examples of how eMaint software can be customized and configured to match different organizations' workflow processes. Key points include:
- Workflow involves systematically organizing resources and roles to streamline operations through repeatable processes.
- eMaint allows customizations like additional tables, fields, and after-save actions to route, prioritize, and notify users of work requests based on building, location, or problem type.
- Configurations can set system options, security, and forms to match each organization's specific needs and processes for request approval, priority setting, and notification.
Business Process Automation and Data Processing WorkflowsMarlon Dumas
Presentation on Business Process Management Systems and Data Processing Workflow Systems delivered at the Italian Statistics Institute (IStat), 3 May 2018.
This document provides steps for configuring and executing a make-to-order process in SAP ERP. It explains how to create materials, bills of materials, routings, sales orders, planned orders, purchase requisitions, purchase orders, goods movements, production orders, and deliveries to fulfill a customer order from sales to delivery. The major steps include sales order creation, planning, external procurement, subcontracting, production, and delivery.
The document discusses Enterprise Resource Planning (ERP) systems. It begins with an introduction to ERP, explaining that ERP systems integrate business functions and processes across an entire organization onto a single computer system in real-time. It then discusses key aspects of ERP including common business modules, implementation considerations, benefits and challenges. Examples of business modules included in ERP systems are finance, manufacturing, human resources and sales. The document emphasizes that for ERP implementations to succeed, organizational processes may need to be reengineered to align with the software.
This document describes a software tool called Control Systems Autogen that can automate the generation of control system documentation and code. It summarizes:
- Autogen can auto-generate PLC code, SCADA graphics, functional descriptions and other artifacts for control systems based on design input data provided by the user, reducing development time by up to 80%.
- The user provides input data like PLC I/O points and properties of controlled equipment in Excel sheets. Autogen then generates code and documentation by replacing tags in template files.
- It supports multiple PLC and SCADA platforms and allows customizing outputs to company standards. Services include customizing Autogen, project management, and consultancy.
The document discusses various aspects of implementing an ERP system, including strategies, challenges, and approaches. It describes the big bang approach where all modules go live at once, replacing the old system entirely. Alternatively, a phased approach implements modules sequentially. A parallel approach runs the old and new systems simultaneously before a switch. Key factors in choosing an approach include company size, centralized processes, and urgency of the ERP solution. Successful implementation depends on careful planning, change management, training, and addressing challenges like resistance to change.
Pankaj Singh has over 15 years of experience in the telecom domain working on prepaid top-up systems, revenue assurance, and provisioning mediation projects. He currently works as a technical team leader at IBM India Private Ltd and has experience leading teams and managing projects for clients like Vodafone and Idea. His technical skills include Java/J2EE, Linux, AIX, SQL, and he has experience with technologies like Tomcat, Oracle, and Comptel.
This document outlines the calibration process for test equipment in SAP PM, including:
1. Creating master inspection characteristics, equipment tasks lists, and maintenance plans for scheduling calibration work.
2. Generating calibration orders, carrying out tasks, and recording calibration results.
3. Making a usage decision based on the results to determine if equipment passes calibration or needs to be deactivated.
The process integrates test equipment management from the SAP Quality Management module with maintenance order processing in PM.
This document provides a system requirements study for an inventory management system called ABC Inventory being developed by ABC company. The system will track parts, finished goods, and transactions in company warehouses. It will interface with existing purchase, production, and customer order systems. Key requirements include compatibility with other systems, high reliability and availability, and the ability to support multiple simultaneous users. The new system must allow adding new parts and goods, issuing parts to manufacturing, entering finished goods, and providing reports. Functionality, interfaces, data requirements, and constraints are defined to guide the development of the new inventory system using an object-oriented approach.
Medical Store Management System Software Engineering 1hani2253
This document outlines a medical store management system project created by three students. The project aims to automate the manual record keeping process of a medical store. Key features of the software include inventory management, accounting, customer management, and reporting. The document discusses the scope, objectives, drawbacks of the current system, and deliverables of the project. It also covers the system requirements, design approach, implementation details, and user documentation.
The document discusses the benefits of SAP's Plant Maintenance (PM) module. The PM module allows companies to: 1) plan and manage preventative maintenance to reduce breakdowns and increase equipment availability; 2) identify and rectify equipment problems whether from failure or deterioration; and 3) break maintenance down into different levels for both planning and performing tasks at either the individual equipment or functional location level. Overall, the PM module standardizes maintenance practices, integrates maintenance with other business functions, and provides structured cost and equipment history data for better resource control and cost management.
The document discusses software configuration management (SCM). It defines SCM as identifying, organizing, and controlling modifications to software being built by a programming team, with the goal of maximizing productivity by minimizing mistakes. SCM involves activities to identify, control, and track changes throughout the software development process. An important part of SCM is the repository, which stores software configuration items and allows developers to manage changes effectively.
Solution Manager - SAP NW BW on HANA Setup Part 3 of 3 (Technical Monitoring ...Linh Nguyen
This document provides instructions for configuring technical monitoring in SAP Solution Manager, including defining the monitoring scope, assigning monitoring templates to managed systems, specifying which metrics will be collected, and checking the monitoring configuration and sample alerts. It emphasizes that setting up Solution Manager monitoring is a multi-step project involving preparing the infrastructure, configuring managed systems, and defining the monitoring scope and reporting.
This document provides an overview of the general store inventory system design project. It includes sections that describe the context diagram, data flow diagrams, entity relationship diagram, class diagram, activity diagram, sequence diagrams, and architecture design. The document also lists the various forms and reports that will be used in the system, such as products, customers, suppliers, transactions, sales, and stock management.
KMR Soft Online Training offers extensive training of corporate employees. KMR Soft team specialize in strive applied solutions and learning platforms ideal to increase your quiescent reach, within the organization to enhance the arena performance. We work out constituent that acquaintance techniques with asynchronous teamwork that helps the organization training techniques more efficiently.
Keynote talk by Marlon Dumas at the Bolzano Rules and Artificial INtelligence Summit (BRAIN 2019), RuleML+RR and GCAI Conferences, Bolzano, Italy, 17 September 2019. The talk gives an overview of state-of-the-art methods in the field of process mining and predictive process monitoring and spells out research challenges in the fields of prescriptive process monitoring and automated process improvement.
This document discusses Function Point Analysis, which is a technique for measuring the size of software systems. It breaks systems into smaller components like external inputs, outputs, inquiries, internal logical files, and external interface files. Counting these components provides a total Function Point that can be used to measure a system's size, track scope changes, and compare productivity across tools and languages. The benefits are that Function Points allow for accurate sizing, can be counted consistently, and help with estimating and communicating a system's size to stakeholders.
The document discusses key aspects of requirements engineering including types of requirements, the requirements engineering process, and techniques used in requirements elicitation and analysis. It describes user requirements, system requirements, functional requirements, non-functional requirements, and domain requirements. The requirements engineering process involves activities like feasibility studies, requirements elicitation and analysis, requirements specification, validation, and management. Requirements elicitation and analysis techniques include requirements discovery, classification, prioritization, documentation, and dealing with issues that can arise.
Function point analysis is a method of estimating the size of a software application based on the user view rather than lines of code. It involves identifying and classifying functional components such as internal logical files, external interface files, inputs, outputs, and inquiries. Each component is assigned a complexity and weight to calculate the total functional size in function points. The size can then be adjusted based on 14 general system characteristics to determine the final adjusted size. The document provides details on the history, vocabulary, types of data and transactions, counting process, and complexity determination involved in function point analysis.
Using Function Point Metrics For Software Economic StudiesCAST
The document discusses the use of function point metrics for software economic studies. It notes that function points are well-suited for productivity analysis as they avoid distortions from lines of code metrics. Function points support various types of analyses including cost, quality, and value studies. The document outlines the evolution and expansion of function point uses from 2010 to 2020, including new domains like delivery, quality, and portfolio analysis. It emphasizes the need to extend function point counting to smaller and larger projects.
Robust configuration management (CM) practices are essential for creating continuous builds to support agile’s integration and testing demands, and for rapidly packaging, releasing, and deploying applications into production. Classic CM—identifying system components, controlling change, reporting the system’s configuration, and auditing—won’t do the trick anymore. Bob Aiello presents an in-depth tour of a more robust and powerful approach to CM consisting of six key functions: source code management, build engineering, environment management, change management and control, release management, and deployment. Bob describes current and emerging CM trends—support for agile development, cloud computing, and mobile apps development—and reviews the industry standards and frameworks essential in CM today. Take back an integrated approach to establish proper IT governance and compliance using the latest CM practices while offering development teams the most effective CM practices available today.
The document discusses workflow and provides examples of how eMaint software can be customized and configured to match different organizations' workflow processes. Key points include:
- Workflow involves systematically organizing resources and roles to streamline operations through repeatable processes.
- eMaint allows customizations like additional tables, fields, and after-save actions to route, prioritize, and notify users of work requests based on building, location, or problem type.
- Configurations can set system options, security, and forms to match each organization's specific needs and processes for request approval, priority setting, and notification.
Business Process Automation and Data Processing WorkflowsMarlon Dumas
Presentation on Business Process Management Systems and Data Processing Workflow Systems delivered at the Italian Statistics Institute (IStat), 3 May 2018.
This document provides steps for configuring and executing a make-to-order process in SAP ERP. It explains how to create materials, bills of materials, routings, sales orders, planned orders, purchase requisitions, purchase orders, goods movements, production orders, and deliveries to fulfill a customer order from sales to delivery. The major steps include sales order creation, planning, external procurement, subcontracting, production, and delivery.
The document discusses Enterprise Resource Planning (ERP) systems. It begins with an introduction to ERP, explaining that ERP systems integrate business functions and processes across an entire organization onto a single computer system in real-time. It then discusses key aspects of ERP including common business modules, implementation considerations, benefits and challenges. Examples of business modules included in ERP systems are finance, manufacturing, human resources and sales. The document emphasizes that for ERP implementations to succeed, organizational processes may need to be reengineered to align with the software.
This document describes a software tool called Control Systems Autogen that can automate the generation of control system documentation and code. It summarizes:
- Autogen can auto-generate PLC code, SCADA graphics, functional descriptions and other artifacts for control systems based on design input data provided by the user, reducing development time by up to 80%.
- The user provides input data like PLC I/O points and properties of controlled equipment in Excel sheets. Autogen then generates code and documentation by replacing tags in template files.
- It supports multiple PLC and SCADA platforms and allows customizing outputs to company standards. Services include customizing Autogen, project management, and consultancy.
The document discusses various aspects of implementing an ERP system, including strategies, challenges, and approaches. It describes the big bang approach where all modules go live at once, replacing the old system entirely. Alternatively, a phased approach implements modules sequentially. A parallel approach runs the old and new systems simultaneously before a switch. Key factors in choosing an approach include company size, centralized processes, and urgency of the ERP solution. Successful implementation depends on careful planning, change management, training, and addressing challenges like resistance to change.
Pankaj Singh has over 15 years of experience in the telecom domain working on prepaid top-up systems, revenue assurance, and provisioning mediation projects. He currently works as a technical team leader at IBM India Private Ltd and has experience leading teams and managing projects for clients like Vodafone and Idea. His technical skills include Java/J2EE, Linux, AIX, SQL, and he has experience with technologies like Tomcat, Oracle, and Comptel.
This document outlines the calibration process for test equipment in SAP PM, including:
1. Creating master inspection characteristics, equipment tasks lists, and maintenance plans for scheduling calibration work.
2. Generating calibration orders, carrying out tasks, and recording calibration results.
3. Making a usage decision based on the results to determine if equipment passes calibration or needs to be deactivated.
The process integrates test equipment management from the SAP Quality Management module with maintenance order processing in PM.
This document provides a system requirements study for an inventory management system called ABC Inventory being developed by ABC company. The system will track parts, finished goods, and transactions in company warehouses. It will interface with existing purchase, production, and customer order systems. Key requirements include compatibility with other systems, high reliability and availability, and the ability to support multiple simultaneous users. The new system must allow adding new parts and goods, issuing parts to manufacturing, entering finished goods, and providing reports. Functionality, interfaces, data requirements, and constraints are defined to guide the development of the new inventory system using an object-oriented approach.
Medical Store Management System Software Engineering 1hani2253
This document outlines a medical store management system project created by three students. The project aims to automate the manual record keeping process of a medical store. Key features of the software include inventory management, accounting, customer management, and reporting. The document discusses the scope, objectives, drawbacks of the current system, and deliverables of the project. It also covers the system requirements, design approach, implementation details, and user documentation.
Medical Store Management System Software Engineering Projecthani2253
This document provides an overview of a medical store management system project. It describes the project title, objectives, features, scope, and deliverables. The project aims to automate the inventory, accounting, and customer management processes of a medical store to ease the workload. It will use a waterfall model and be developed in Java. Key features will include product, customer, sales, and payment management. The document outlines requirements, design, and implementation plans including user stories, data flow diagrams, and a work breakdown structure.
The document discusses different software engineering process models including:
1. The waterfall model which is a linear sequential model where each phase must be completed before moving to the next.
2. Prototyping models which allow requirements to be refined through building prototypes.
3. RAD (Rapid Application Development) which emphasizes short development cycles through reuse and code generation.
4. Incremental models which deliver functionality in increments with early increments focusing on high priority requirements.
5. The spiral model which has multiple iterations of planning, risk analysis, engineering and evaluation phases.
This document discusses software engineering and requirements engineering. It defines software engineering as using techniques, methodologies and tools to produce high quality software within budget and deadline constraints. It describes requirements engineering as identifying functional, non-functional and pseudo requirements to develop software. Key activities in requirements engineering include domain analysis, defining the problem scope, and determining what constitutes a requirement.
The document discusses various aspects of designing testing in a perfect versus realistic world. It covers topics such as:
1. What is considered a perfect world for testing and how it differs from reality.
2. The value a tester provides by being the first user to experience a system and find low severity defects.
3. Aspects of a smart test design such as using inputs from multiple sources, limiting dependencies, and focusing on business use cases.
4. How to design tests from start to finish and represent business processes at different design levels.
5. The advantages of different testing approaches and finding a balance point between simplicity and complexity.
6. Ways to present data coverage and
1. The document discusses various software engineering process models including waterfall, prototyping, RAD, incremental, and spiral models. It describes the key phases and advantages/disadvantages of each.
2. It also covers system engineering and how software engineering occurs as part of developing larger systems. Business process engineering and product engineering are introduced for developing information systems and products respectively.
3. Key aspects of developing computer-based systems are outlined including the elements of software, hardware, people, databases, documentation and procedures.
Nesma autumn conference 2015 - Is FPA a valuable addition to predictable agil...Nesma
This document discusses using Function Point Analysis (FPA) as a metric for Agile software projects. It provides context on replacing an existing trading system and outlines an architecture and development approach using Agile/Scrum. Metrics are proposed for use at the sprint level and cumulatively, including function points, story points, lines of code, and productivity rates. FPA is argued to provide benefits for scope management, benchmarking, and proving productivity and quality for Agile projects. Contracting based on function points is also discussed.
Software requirement engineering bridges the gap between system engineering and software design. It involves gathering requirements through elicitation techniques like interviews and facilitated application specification technique (FAST), analyzing requirements, modeling them, specifying them in documents like use cases, and reviewing the requirements specification. Quality function deployment translates customer needs into technical requirements. Rapid prototyping helps validate requirements by constructing a partial system implementation using tools like 4GLs, reusable components, or formal specification languages. The software requirements specification document is produced at the end of analysis and acts as a contract between developers and customers.
Software is a set of instructions and data structures that enable computer programs to provide desired functions and manipulate information. Software engineering is the systematic development and maintenance of software. It differs from software programming in that engineering involves teams developing complex, long-lasting systems through roles like architect and manager, while programming involves single developers building small, short-term applications. A software development life cycle like waterfall or spiral model provides structure to a project through phases from requirements to maintenance. Rapid application development emphasizes short cycles through business, data, and process modeling to create reusable components and reduce testing time.
The document discusses Enterprise Resource Planning (ERP) systems. It describes the ERP architecture as using a client-server model with a relational database to store and process data. The ERP lifecycle involves definition, construction, implementation, and operation phases. Core ERP components manage accounting, production, human resources and other internal functions, while extended components provide external capabilities like CRM, SCM, and e-business. Proper implementation requires screening software, evaluating packages, analyzing process gaps, reengineering workflows, training staff, testing, and post-implementation support.
The document provides an overview of fundamentals of software development including definitions of software, characteristics of software, software engineering, layered approach to software engineering, need for software engineering, and common software development life cycle models. It describes system software and application software. It outlines characteristics like understandability, cost, maintainability, modularity, reliability, portability, documentation, reusability, and interoperability. It also defines software engineering, layered approach, and need for software engineering. Finally, it explains popular life cycle models like waterfall, iterative waterfall, prototyping, spiral, and RAD models.
The document provides an introduction to software engineering and discusses key concepts such as:
1) Software is defined as a set of instructions that provide desired features, functions, and performance when executed and includes programs, data, and documentation.
2) Software engineering applies scientific knowledge and engineering principles to the development of reliable and efficient software within time and budget constraints.
3) The software development life cycle (SDLC) involves analysis, design, implementation, and documentation phases to systematically develop high quality software that meets requirements.
The document outlines requirements for automating store management functions. It describes the need to automate processes like product details handling, refilling stocks, and financial analysis. The system would allow administrators, employees, dealers and customers to access features after login. Key features include adding new products, searching and updating product information, dealer management, report generation, and storing data in a database. The system is intended to improve efficiency, security, accuracy and reliability over a manual process. It specifies functional and non-functional requirements including user authentication, performance standards, and interfaces for hardware, software and users.
This document provides an overview and outline of an HR Management System project. It includes sections on the current problems with the existing system, the proposed new system, key modules like Time Management and ATS (Apprentice Training), and technologies used like .NET, C#, Oracle 11g, and the Spiral model of software development. Feasibility aspects like technical, economic and operational feasibility are also summarized. The goal of the project is to develop a centralized web-based system to replace manual and decentralized existing systems for better management of employee attendance, leave, payroll and student training functions.
Sales and inventory management system project reportFuckboy123
This document provides a project report on developing a Sales and Inventory Management System. It includes sections on system introduction, problems with the existing manual system, scope of the proposed computerized system, feasibility study, hardware and software requirements, proposed system features including use case diagrams, class diagram, input screens, and table specifications. The objectives are to keep records of complete inventory, track materials by quantity and value, and improve visibility, cash flow and decision making for inventory and warehouse management.
This document provides an overview of the approach and key considerations for upgrading an Oracle E-Business Suite instance from Release 11i to Release 12. It discusses conducting functional and technical discovery analyses, building and testing the new version, preparing end users, and executing the cutover. It also highlights some new features in R12 like assigning item images in iProcurement, enhanced security for concurrent program access, using custom payment formats, and the ability to generate accounting entries from revenue distribution accounts using sub-ledger accounting functionality.
The document discusses interaction design and the design process for interactive systems. It covers identifying user requirements, conceptual and physical design, prototyping and evaluation. The design process involves requirements specification, architectural design, detailed design, coding, testing, and maintenance. Iterative design and user evaluation are important to develop an acceptable product. Capturing the design rationale helps communicate decisions and supports reuse.
Similar to Project Management (Practical Qustion Paper) [CBSGS - 75:25 Pattern] {2013-2014: Manual} (20)
Linux System Administration (November – 2018) [Choice Based | Question Paper]Mumbai B.Sc.IT Study
This document contains questions for an exam on Linux System Administration. It covers topics such as piping and redirecting commands, the duties of a Linux system administrator, find commands, process management commands, hard and symbolic links, RPM and YUM, Linux partitions, file systems, runlevels and services, enabling SSH, managing users and groups, firewalls, iptables tables and rules, encrypting and decrypting files, NFS, Samba file servers, DNS hierarchy, dhcp.conf parameters, MTA and MDA, Apache configuration, virtual hosts, shell script elements, script to create a directory, high-availability clusters, bonding devices, TFTP servers, and Kickstart files. The exam expects students to answer 15 marks
Advanced Web Programming (November – 2018) [Choice Based | Question Paper]Mumbai B.Sc.IT Study
This document outlines the questions and structure for an exam on Advanced Web Programming. It includes 15 questions across 5 sections. The questions cover topics like namespaces, arrays, .NET framework architecture, inheritance, constructors, delegates, validation controls, exceptions, debugging, cookies, viewstate, CSS, ADO.NET objects, data readers, gridviews, authentication, impersonation, and AJAX controls. Students must attempt 3 questions from each section, for a total of 15 questions and a maximum of 75 points on the exam. Diagrams and examples are encouraged for full marks.
Artificial Intelligence (November – 2018) [Choice Based | Question Paper]Mumbai B.Sc.IT Study
This document contains instructions and questions for an Artificial Intelligence exam. It is divided into 5 sections, with 3 questions in each section worth 15 marks each. The questions cover a range of topics in AI including agents and environments, search algorithms, logic, knowledge representation, planning and other concepts. Students must attempt 3 questions out of 6 in each section. Diagrams and examples should be provided where necessary. Calculators and electronic devices are not permitted.
Software Project Management (November – 2018) [Choice Based | Question Paper]Mumbai B.Sc.IT Study
This document outlines the structure and questions for an exam on software project management. It contains 5 sections with 3 questions each, for a total of 15 questions. Students must answer 3 questions from each section for a total of 9 questions. The questions cover a range of topics in software project management, including project life cycles, project charters, portfolio management, estimation techniques, scheduling, risk management, configuration management, contract types, and project organization. The exam is 2.5 hours long and worth a total of 75 marks.
Next Generation Technologies (November – 2018) [Choice Based | Question Paper]Mumbai B.Sc.IT Study
This document outlines the structure and questions for a B.Sc. IT semester 5 exam focusing on next generation technologies. It contains 5 sections with 3 questions each, covering topics like Big Data, NoSQL databases, MongoDB, jQuery, JSON, and more. Students must attempt 3 questions from each section. The exam is 2.5 hours long and carries a total of 75 marks. Diagrams and examples should be provided as needed. Use of calculators or other electronic devices is not permitted during the exam.
Internet Of Things (November – 2018) [Choice Based | Question Paper]Mumbai B.Sc.IT Study
This document is an exam paper for the subject Internet of Things from Mumbai University. It contains 15 questions divided into 5 sections. Section 1 contains 6 questions on defining and explaining key concepts related to IoT. Section 2 contains 6 questions on prototyping embedded devices and comparing development platforms like Arduino and Raspberry Pi. Section 3 contains 6 questions on different methods of prototyping like non-digital methods, 3D printing and laser cutting. Section 4 contains 6 questions on limitations of memory in embedded systems, performance concerns and libraries. Section 5 contains 6 questions on designing PCBs, certification of IoT devices, privacy concerns and the sensor commons project. Students have to attempt 3 questions from each section and the exam is
Enterprise Java (November – 2018) [Choice Based | Question Paper]Mumbai B.Sc.IT Study
This document outlines the structure and content of an exam for an Enterprise Java course. The exam contains 5 questions, with students required to answer 3 sub-questions from each question. Question topics include Java EE container architectures, the servlet lifecycle, HTTP session management, JSP directives and expression language, enterprise beans, JNDI lookup, Hibernate architecture and components, and object-relational impedance mismatch. The exam is 2.5 hours long and worth a total of 75 marks. Students are instructed to write question numbers clearly and not mix sub-question responses. Diagrams and examples are encouraged where necessary.
Project Management (April - 2016) [CBSGS - Paper Solution] {Mumbai University}Mumbai B.Sc.IT Study
The document provides information about a project management textbook for the BSc IT program at Mumbai University. It includes details like the university, course, semester, subject, and author. The author, Kamal Thakur, provides his contact information and outlines the contents of the textbook, which covers topics like software development planning, requirements, architecture, automation, metrics, and future trends in project management. It contains several chapters with questions and solutions related to project management concepts.
Project Management (April - 2015) [CBSGS - Paper Solution] {Mumbai University}Mumbai B.Sc.IT Study
This document provides information about a project management paper solution from Mumbai University for the B.Sc. IT program. It includes the university details, course information, author information, and the paper solution content which is divided into 7 questions. The paper solution covers topics like software lifecycles, artifacts, architecture, estimation techniques, roles, automation, and metrics. Contact information is also provided for the author.
Project Management (October - 2015) [CBSGS - Paper Solution] {Mumbai University}Mumbai B.Sc.IT Study
This document provides information about a project management paper solution from Mumbai University for the B.Sc. IT program. It includes the university details, course information, author information, and the paper itself which contains 7 sections with multiple choice questions covering various aspects of project management like the project life cycle, cost estimation, quality parameters, workflows, and more.
CapTechTalks Webinar Slides June 2024 Donovan Wright.pptxCapitolTechU
Slides from a Capitol Technology University webinar held June 20, 2024. The webinar featured Dr. Donovan Wright, presenting on the Department of Defense Digital Transformation.
Brand Guideline of Bashundhara A4 Paper - 2024khabri85
It outlines the basic identity elements such as symbol, logotype, colors, and typefaces. It provides examples of applying the identity to materials like letterhead, business cards, reports, folders, and websites.
Get Success with the Latest UiPath UIPATH-ADPV1 Exam Dumps (V11.02) 2024yarusun
Are you worried about your preparation for the UiPath Power Platform Functional Consultant Certification Exam? You can come to DumpsBase to download the latest UiPath UIPATH-ADPV1 exam dumps (V11.02) to evaluate your preparation for the UIPATH-ADPV1 exam with the PDF format and testing engine software. The latest UiPath UIPATH-ADPV1 exam questions and answers go over every subject on the exam so you can easily understand them. You won't need to worry about passing the UIPATH-ADPV1 exam if you master all of these UiPath UIPATH-ADPV1 dumps (V11.02) of DumpsBase. #UIPATH-ADPV1 Dumps #UIPATH-ADPV1 #UIPATH-ADPV1 Exam Dumps
Information and Communication Technology in EducationMJDuyan
(𝐓𝐋𝐄 𝟏𝟎𝟎) (𝐋𝐞𝐬𝐬𝐨𝐧 2)-𝐏𝐫𝐞𝐥𝐢𝐦𝐬
𝐄𝐱𝐩𝐥𝐚𝐢𝐧 𝐭𝐡𝐞 𝐈𝐂𝐓 𝐢𝐧 𝐞𝐝𝐮𝐜𝐚𝐭𝐢𝐨𝐧:
Students will be able to explain the role and impact of Information and Communication Technology (ICT) in education. They will understand how ICT tools, such as computers, the internet, and educational software, enhance learning and teaching processes. By exploring various ICT applications, students will recognize how these technologies facilitate access to information, improve communication, support collaboration, and enable personalized learning experiences.
𝐃𝐢𝐬𝐜𝐮𝐬𝐬 𝐭𝐡𝐞 𝐫𝐞𝐥𝐢𝐚𝐛𝐥𝐞 𝐬𝐨𝐮𝐫𝐜𝐞𝐬 𝐨𝐧 𝐭𝐡𝐞 𝐢𝐧𝐭𝐞𝐫𝐧𝐞𝐭:
-Students will be able to discuss what constitutes reliable sources on the internet. They will learn to identify key characteristics of trustworthy information, such as credibility, accuracy, and authority. By examining different types of online sources, students will develop skills to evaluate the reliability of websites and content, ensuring they can distinguish between reputable information and misinformation.
(𝐓𝐋𝐄 𝟏𝟎𝟎) (𝐋𝐞𝐬𝐬𝐨𝐧 3)-𝐏𝐫𝐞𝐥𝐢𝐦𝐬
Lesson Outcomes:
- students will be able to identify and name various types of ornamental plants commonly used in landscaping and decoration, classifying them based on their characteristics such as foliage, flowering, and growth habits. They will understand the ecological, aesthetic, and economic benefits of ornamental plants, including their roles in improving air quality, providing habitats for wildlife, and enhancing the visual appeal of environments. Additionally, students will demonstrate knowledge of the basic requirements for growing ornamental plants, ensuring they can effectively cultivate and maintain these plants in various settings.
Creativity for Innovation and SpeechmakingMattVassar1
Tapping into the creative side of your brain to come up with truly innovative approaches. These strategies are based on original research from Stanford University lecturer Matt Vassar, where he discusses how you can use them to come up with truly innovative solutions, regardless of whether you're using to come up with a creative and memorable angle for a business pitch--or if you're coming up with business or technical innovations.
Post init hook in the odoo 17 ERP ModuleCeline George
In Odoo, hooks are functions that are presented as a string in the __init__ file of a module. They are the functions that can execute before and after the existing code.
2. TYBSc(IT) Semester VI
Credit Based Semester and Grading System
Paper II – Project Management
Reference Manual for Instructors for Conducting Practicals
Developed & Compiled By
Mr. Hiren Dand, MCC
&
Mrs. R. Srivaramangai, UDIT
2013 – 2014
3. Requirements :
1. Ms Project
2. StarUML
3. WBSPro(Optional)
Practical No. 1 : SYSTEM REQUIREMENT STUDY (SRS) FOR A PROJECT
Case :
ABC company wishes to create a small software program for keeping the stock of their goods
especially the raw materials. This they named as ABC_Inventory and would like to deploy their
in-house development cell for the development.
Aim:
TO Describe the System Requirement Study of your Project ( in this case the ABC Inventory)with
necessary illustrations and following the standards
Objective : ABC Inventory’s main objective is to keep track of all the parts and finished goods in
the warehouses and all the transactions involving these parts and goods.
Introduction
Currently the Inventory is carried out in the traditional way and the information of the products,
supplier, orders etc are kept in an Excel workbook. The project is aimed in such a way that it
should be possible for the new system to interact with the already existing systems or may with
the newer systems that may be created. Other existing systems are :
1. Purchase
2. Production
3. Customer Order Entry/Shipping
4. Subsystems
The Inventory Control System (ICS) known as ABC Inventory will work in the existing Enterprise
Planning System (ERP) system.
Overall Description
The newly developed system will be invoked mainly when:
– purchased goods arrive from vendors,
– goods are returned to the vendor for various reasons,
4. – stock is issued to/from manufacturing,
– finished goods are entered in the Finished Goods Warehouse
– finished goods are shipped to the customer
– sales persons wish to check the availability of products.
• Interface with Purchasing:
When an order from a vendor arrives, our Purchase Order Number on the vendor’s
invoice will be used to locate the the PO and other related documents, such as vendor
proposals, price lists, product specifications.
These will then be forwarded to Quality Control to be used in the inspection of the
goods.
An interface will be worked out with Purchasing subsystem currently running on Server
PS1 so that ICS can find all documents related to the current purchase.
• Interface with Manufacturing:
Mfg requests materials
Mfg wants to store finished goods
• Interface with Customer Order Entry/Shipping:
COES wants to ship goods
COES wants to store returned goods
5. An automatic purchase order generation should be provisioned when the stock levels of parts
falls below the minimum has been contemplated but postponed to a future date.
The main functions of system are:
• Entering new parts into the inventory
• Issuing parts to Manufacturing
• Entering finished goods to the inventory
• It also should:
• Provide a user interface consistent with the other subsystems
• Verify user identities and access rights
• Do error checking on all inputs
• Permit users to add customized reports
Project Constraints
• Compatibility
• The software should run compatibly (i.e. under the same operating system,
database and networking capabilities) with the other subsystems software it
works together with.
• It should allow an Administrator to enroll new users and give them access rights
required by their duties.
• Reliability and Availability
• Since it interfaces with Purchasing, Customer Order Entry and Manufacturing, it
should be available as a minimum when any one of these subsystems are
available.
• It should permit 1 hour per day for maintenance and backup activities with
minimal disruption to users.
• Any failure should cause no more than 10-minute downtime, with the average not
exceeding 2 minutes.
• Backup should spot-tested to ensure they are reliable.
• Performance
6. • It should allow up to 10 users to logon simultaneously and receive an average
response time not exceeding 3 seconds.
• Parts received should be in the recorded in the system in no more than 2 hours,
with the average under 30 minutes.
External Information from other subsystems to be used by Inventory System
1. Vendor Order Master File - Purchasing
2. Vendor Order Detail File - Purchasing
3. Customer Order Master File – Customer Order Entry
4. Customer Order Detail File – Customer Order Entry
5. Manufacturing Requests – Manufacturing
6. Manufacturing Schedule– Manufacturing
System’s Own information storage
1. Part Transaction File
2. Part Master File
3. Part Detail File
4. Part Inventory File
Major Transactions to be provided by the system are:
– Create New Part or Product Master Record
Edit/Delete Part or Product Master Record
– Edit/Delete Part or Product Record
– Enter New Part or Product
– Enter Returned Part or Product
– Issue Part or Product
– Re-issue Part or Product
– View Part or Product
Detailed description of the Transactions
For Creation of Products/Parts
7. Narrative: Creates a new part or product type. After the type has been created, part or product
instances can be entered. Permits user to enter a new type code and its description. The type
code should be selected according to the “Part/product Type Code Guidelines” document. Uses
PartMaster Class and PartDetail Class.
Constraints:
Requires “Product Administrator” rights for use.
Performance constraints: Since it locks PartMaster, the transaction should time-out after 15
seconds and backout all changes.
Design Constraints: Must check type code for compliance with Guidelines
Supporting Diagrams: See Class diagram for PartMaster and Part Detail classes.
For Modification and Deletion of Parts
Permits user to edit the description of a part or product or delete it. If there are any instances of
the part or product, it can not be deleted. Uses PartMaster Class, PartDetail Class and
PartInventory Class.
Constraints:
Requires “Product Administrator” rights for use.
Performance constraints: Since it locks PartMaster, PartDetail and PartInventory Classes, the
transaction should time-out after 15 seconds and backout all changes.
Design Constraints: Must check type code for compliance with Guidelines. Any instances of the
part or product are in existence, only certain fields may be edited.
Methodology adopted :
Object oriented approach since the components created can be reused later on in other
susystems. Scalability and Reliability also makes it towards object orientation.
So the requirement specifications are to be done with UML diagrams for the front – end and
processing which consists of
Use case diagrams
Acitvity diagrams
Sequence diagrams
8. Class diagrams
An E-R model will help to imcorporate the information storage in the form of relational tables in
the chosen ORDBMS environment
Before placing the SRS, feasibility study needs to be done. The overall methodology and
description constitutes the SRS of the system
Practical No. 2 : Waterfall Model as the conventional process model to prepare the flow and
Gantt Chart
To be done as per Software Engineering approach for any project preferably the student’s project
using waterfall model as the process model and to prepare the scheduling chart using Gantt chart
Practical No. 3 : Cost Estimation of the project Using Function Point Analysis (FPA)
What is Function Point Analysis (FPA)?
• It is designed to estimate and measure the time, and thereby the cost, of developing
new software applications and maintaining existing software applications.
• It is also useful in comparing and highlighting opportunities for productivity
improvements in software development.
• It was developed by A.J. Albrecht of the IBM Corporation in the early 1980s.
• The main other approach used for measuring the size, and therefore the time required,
of software project is lines of code (LOC) – which has a number of inherent problems.
How is Function Point Analysis done?
Working from the project design specifications, the following system functions are measured
(counted):
• Inputs
• Outputs
• Files
• Inquires
• Interfaces
9. These function-point counts are then weighed (multiplied) by their degree of complexity:
Simple Average Complex
Inputs 2 4 6
Outputs 3 5 7
Files 5 10 15
Inquires 2 4 6
Interfaces 4 7 10
A simple example:
inputs
3 simple X 2 = 6
4 average X 4 = 16
1 complex X 6 = 6
outputs
6 average X 5 = 30
2 complex X 7 = 14
files
5 complex X 15 = 75
inquiries
8 average X 4 = 32
interfaces
3 average X 7 = 21
4 complex X 10 = 40
Unadjusted function points 240
• There are 14 more “Degree of Influences” ( 0 to 5 scale) :
• data communications
• distributed data processing
10. • performance criteria
• heavy hardware utilization
• high transaction rate
• online data entry
• end user efficiency
• on-line update
• complex computation
• reusability
• ease of installation
• ease of operation
• portability
• maintainability
• Define Technical Complexity Factor (TCF):
• TCF = .65 + [(.01) x (14 DIs )]
• where DI = ∑ ( influence factor value)
Function Point = Initial FP X TCF.
But how long will the project take and how much will it cost?
• Suppose programmers in our organization average 18 function points per month and
suppose the Function Point is 197
197 FP divided by 18 = 11 man-months
• If the average programmer is paid $5,200 per month (including benefits), then the [labor]
cost of the project will be . . .
11 man-months X $5,200 = $57,200
The total cost for far estimated is $57,200
Practical No. 4 : Cost Estimation of the project Using COCOMO Model I
Software cost estimation is important for making good management decisions. It is also
connected to determining how much effort and time a software project requires. The
11. COnstructive COst MOdel ( COCOMO) is an example of regression models used for estimating
software cost and effort. These methods use a basic formula with parameters that are
determined via a historical database and current project characteristics.
The Basic COCOMO Model:
The Basic Model makes its estimates of required effort ( measured in Staff-Months SM ) based
primarily on your estimate of the software project's size ( as measured in thousands of Delivered
Source Instructions KDSI ):
SM = a * ( KDSI )b
The Basic model also presents an equation for estimating the development schedule ( Time of
Develop TDEV ) of the project in months:
TDEV= c * ( SM )d
Following questions are to be answered before proceeding with the calculation.
• Which Instructions count as delivered source instructions?
• Which Staff-Months are included in the estimate?
• Which phases are included in "development" ?
• What classes of projects are covered by the estimating equations?
Definitions and Assumptions while estimating COCOMO model I
1. The primary cost driver is the number of delivered source instructions ( DSI ) developed
by the project. DSI is defined such that:
o Only source lines that are DELIVERED as part of the product are included.
Therefore test drivers and other support software are excluded.
o SOURCE codes, created by project staff and processed into machine code by some
combination of pre-processors, compilers, and assemblers. Code created by
applications generators is excluded.
o INSTRUCTIONS are defined as lines of code or card images. Declarations are
counted as instructions but Comments are excluded.
2. The COCOMO cost estimates only cover the period between beginning of the design phase
and end of the integration and test phase. Costs and schedules of other phases ( like
requirement phase) are estimated separately.
3. A COCOMO Staff-Month ( SM ) consists of 152 hours of working time. This has to be
found to be consistent with practical experience with the average monthly time due to
holidays, vacation and sick leaves. COCOMO avoids estimating labour costs in dollars
because of the large variations between organizations in what is included in labour costs
and because SM is a more stable unit than dollars. After estimating the effort in SM we
convert it into dollar estimate by applying different average dollar per Staff-Month figure
for each major phase, to account for inflation and the difference in salary level of the people
required for each phase.For example, the senior staff (with high salary )are heavily
12. involved in the requirement and early design phases while junior staff ( less salary ) are
more involved in later phases ( detailed design, code and test phases) Therefore the average
SM is higher for early phases.
4. COCOMO assumes that the requirement specification is not substantially changed after the
plans and requirement phase.Any significant modification should be covered by a revised
cost estimate.
5. The detailed COCOMO model assumes that the influence of the software cost drivers is
phase dependent. Basic COCOMO and Intermediate COCOMO do not, except for
distinguishing between development and maintenance.
The Development Mode:
There are several modes of software development .These different software development modes
have cost-estimating relationships which are similar in form, but which yield significantly different
cost estimates for software products of the same size.In the COCOMO Model, one of the most
important factors contributing to a project's duration and cost is the Development mode. Every
project is considered to be developed in one of three modes:
• Organic Mode.
• Semidetached Mode
• Embedded Mode
To estimate the effort and development time, COCOMO use the same equations but with different
coefficients ( a, b, c, d in the effort and schedule equations ) for each development mode. Therefore
before using the COCOMO model we must be able to recognise the development mode of our
project.
1. Organic Mode:
In the organic mode the project is developed in a familiar, stable environment and the
product is similar to previously developed products. The product is relatively small, and
require little innovation. Most people connected with the project have extensive experience
in working with related systems within the organization and therefore can usefully
contribute to the project in its early stages, without generating a great deal of project
communication overhead. An organic mode project is relatively relaxed about the way the
software meets its requirements and interface specifications. If a situation arises where an
exact correspondence of the software product to the original requirements would cause an
extensive rework, the project team can generally negotiate a modification of the
specifications that can be developed more easily.
The Basic COCOMO Effort and schedule equations for organic mode software projects
are:
SM = 2.4 * ( KDSI )1.05
TDEV= 2.50 * ( SM )0.38
13. 2. Semidetached Mode:
In this mode project's characteristics are intermediate between Organic and Embedded.
"Intermediate" may mean either of two things:
1. An intermediate level of project characteristics.
2. A mixture of the organic and embedded mode characteristics.
Therefore in an Semidetached mode project, it is possible that:
o The team members all have an intermediate level of experience with related
systems.
o The team has a wide mixture of experienced and inexperienced people.
o The team members have experience related to some aspects of the system under
development, but not others.
The size of a Semidetached mode product generally extends up to 300 KDSI.
The Basic COCOMO Effort and schedule equations for organic mode software projects
are:
SM = 3.0 * ( KDSI )1.12
TDEV= 2.50 * ( SM )0.35
Embedded Mode:
In this development mode Project is characterized by tight , inflexible constraints and interface
requirements. The product must operate within a strongly coupled complex of hardware, software,
regulations, and operational procedures. The embedded-mode project does not generally have the
option of negotiating easier software changes and fixes by modifying the requirements and
interface specifications.The project therefore need more effort to accommodate changes and fixes.
The embedded mode project is generally charting its way through unknown territory to a greater
extent than the organic mode project. This lead the project to use a much smaller team of analyst
in the early stages, as a large number of people would get swamped in communication overhead.
Once the embedded mode project has completed its product design, its best strategy is to bring on
a very large team of programmers to perform detailed design, coding and unit testing in parallel.
Otherwise the project would take much longer to complete. This strategy as we will see leads to
the higher peaks in the personnel curves of embedded-mode projects, and to the greater amount of
effort consumed compared to an organic mode project working to the same total development
schedule.
The Basic COCOMO Effort and schedule equations for organic mode software projects are:
SM = 3.6 * ( KDSI )1.20
14. TDEV= 2.50 * ( SM )0.32
Problem : An initial study has determined that the size of the program will be roughly 52,000
delivered source instructions for ABC Inventory.
This project is a good example of an organic-mode software project. Using the Basic COCOMO
equations for this development mode we have:
Effort :
SM = 2.4*(52)1.05
= 152 Staff-Months
Productivity:
52000DSI / 152 SM = 342 DSI / SM
Duration and Staffing:
Once an estimate is obtained for effort ( Staff-Month ), The project manager must determine how
many persons to put on the job. This will ultimately determine the calendar duration of the project.
It is very important to note that more staff does not mean proportionately less calendar time. More
staff complicate communications and this complexity translates into a project slowdown. The
second equation of the COCOMO model use the estimated effort of the project ( SM ) to suggest
the optimum calendar duration of the project. For the example above with estimated effort of 152
SM we have:
Schedule:
TDEM = 2.5 * ( 152 )0.38
= 16 months 8 days( 17 months)
After estimating the duration of the project the manager can easily determine how many persons
in the average must be put on the project:
Average Staffing:
152 staff-months / 17 months = 9 FSP ( Full Time Equivalent Software Personnel )
Phase Distribution of Effort and Schedule for Organic Mode:
After estimating the effort an schedule of a project we need to determine how to distribute them
among different phases of the project.This distribution varies as a function of the size of the
product.Larger software projects require relatively more time and effort to perform integration and
test activities, and are able to compress the programming portion of the program by having larger
number of peoples programming components in parallel. Smaller software projects have a more
15. uniform, flat distribution of labour throughout the development cycle, and have relatively more
resources devoted to the phases other than integration and test.Table 1 and Table 2 present the
percentage distribution of the basic software effort and schedule within the development phases of
an organic mode product:
Table 1 - Phase Distribution of Effort: Organic Mode
Phase
Small ( 2
KDSI)
Intermediate(8
KDSI)
Medium( 32
KDSI )
Large( 128
KDSI )
Plans &
Requirements
6% 6% 6% 6%
Product
Design
16 16 16 16
Detailed
Design
26 25 24 23
Code & Unit
Test
42 40 38 36
Integration &
Test
16 19 22 25
Total: 100 100 100 100
Table 2 - Phase Distribution of Schedule: Oraganic Mode
Phase
Small ( 2
KDSI)
Intermediate(8
KDSI)
Medium( 32
KDSI )
Large( 128
KDSI )
Plans &
Requirements
10% 11% 12% 13%
Product
Design
19 19 19 19
Detailed
Design &
Code & Unit
Test
63 59 55 51
Integration &
Test
18 22 26 30
Total: 100 100 100 100
16. Using table 1 and table 2 we can calculate the number of staff needed for programming ( Detailed
Design & Code and Unit Test ) phase of the previous example:
Programming Effort :
( 0.62 ) ( 152 SM )= 94 Staff-Months
Programming Schedule:
( 0.55 ) ( 17 )= 9 months
Average Staffing:
94 staff-months / 9 months = 10.4 FSP ( Full Time Equivalent Software Personnel )
Phase Distribution of Effort and Schedule for Other Modes:
Table 3 and Table 4 present the percentage distribution of the basic software effort and schedule
within the development phases of an semidetached mode product:
Table 3 - Phase Distribution of Effort: Semidetached Mode
Phase
Small ( 2
KDSI)
Intermediate(8
KDSI)
Medium( 32
KDSI )
Large( 128
KDSI )
Plans &
Requirements
7% 7% 7% 7%
Product
Design
17 17 17 17
Detailed
Design
27 26 25 24
Code & Unit
Test
37 35 33 31
Integration &
Test
19 22 25 28
Total: 100 100 100 100
17. Table 4 - Phase Distribution of Schedule: Semidetached Mode
Phase
Small ( 2
KDSI)
Intermediate(8
KDSI)
Medium( 32
KDSI )
Large( 128
KDSI )
Plans &
Requirements
16% 18% 20% 22%
Product
Design
24 25 26 27
Detailed
Design &
Code & Unit
Test
56 52 48 44
Integration &
Test
20 23 26 29
Total: 100 100 100 100
Table 5 and Table 6 present the percentage distribution of the basic software effort and schedule
within the development phases of an embedded mode product:
Table 3 - Phase Distribution of Effort: Embedded Mode
Phase
Small ( 2
KDSI)
Intermediate(8
KDSI)
Medium( 32
KDSI )
Large( 128
KDSI )
Plans &
Requirements
8% 8% 8% 8%
Product
Design
18 18 18 18
Detailed
Design
28 27 26 25
Code & Unit
Test
32 30 28 26
Integration &
Test
22 25 28 31
Total: 100 100 100 100
Table 4 - Phase Distribution of Schedule: Embedded Mode
18. Phase
Small ( 2
KDSI)
Intermediate(8
KDSI)
Medium( 32
KDSI )
Large( 128
KDSI )
Plans &
Requirements
24% 28% 32% 36%
Product
Design
30 32 34 36
Detailed
Design &
Code & Unit
Test
48 44 40 36
Integration &
Test
22 24 26 28
Total: 100 100 100 100
By comparing tables 1 through 6 we can see some differences between the effort and schedule
distribution of the products developed in different modes. The main differences are:
The embedded-mode project consumes considerably more effort in the integration and test phase.
This results from the need to follow and verify software requirements and interface specifications
more carefully in the embedded and semidetached mode.
The embedded-mode project consumes proportionally less effort in the code and unit test phase.
This results from the proportionally higher effort required for the other development phases.
The embedded-mode project consumes considerably more schedule in both the plans and
requirement phase and the product design phase. This is because of the project's need for more
thorough, validated requirements and design specifications, and the greater need to perform these
phases with a relatively small number of people.
The embedded-mode project consumes considerably less schedule in the programming phase. This
results from the strategy of employing a great many people programming in parallel, in order to
reduce the project's overall schedule.
Intermediate COCOMO Model:
The Intermediate COCOMO is an extension of the basic COCOMO model. Here we use the same
basic equation for the model. But coefficients are slightly different for the effort equation.Also in
addition to the size as the basic cost driver we use 15 more predictor variables. these added cost
drivers help to estimate effort and cost with more accuracy.
An estimator looks closely at many factors of a project such as amount of external storage required,
execution speed constraints, experience of the programmers on the team, experience with the
19. implementation language, use of software tools, etc., for each characteristic, the estimator decide
where on the scale of "very low" , " low", " Nominal", "High", "Very High" and "High" the project
falls. Each characteristic gives an adjustment factor( from the table 7 ) and all factors are multiplied
together to to give an Effort Adjustment Factor ( EAF).If a project is judged normal in some
characteristic the adjustment factor will be 1 for that characteristic ( Nominal column in Table 7 ),
which means that that factor has no effect on overall EAF. The effort equation for the intermediate
model has the form of:
SM = EAF * a * ( KDSI )b
If we assume that the project is "Nominal" in every aspect then all adjustment factors would be 1,
which results in EAF=1, and the effort equation would have the same form as the Basic mode.
in addition to the EAF the model parameter "a" is slightly different in Intermediate COCOMO, but
the "b" parameter is the same.The effort equation for different modes of Intermediate COCOMO
is given in the following table:
Development Mode
Intermediate Effort
Equation
Organic:
SM = EAF * 3.2 * ( KDSI
)1.05
SemiDetached
SM = EAF * 3.0* ( KDSI
)1.12
Embedded
SM = EAF * 2.8* ( KDSI
)1.20
Bohem in Software Engineering Economics defines each of the cost drivers, and defines the Effort
Multiplier associated with each rating ( Table 7 ).
Table 7 - Project Characteristic Table
Cost Driver Very Low Low Nominal High Very High Extra High
ACAP
Analyst
Capability
1.46 1.19 1.00 0.86 0.71 --
AEXP
Application
Experience
1.29 1.13 1.00 0.91 0.82 --
CPLX
Product
Complexity
0.70 0.85 1.00 1.15 1.30 1.65
DATA
Database
Size
-- 0.94 1.00 1.08 1.16 --
LEXP
Language
Experience
1.14 1.07 1.00 0.95 -- --
20. MODP
Modem
Programming
Practices
1.24 1.10 1.00 0.91 0.82 --
PCAP
Programmer
Capability
1.42 1.17 1.00 0.86 0.70 --
RELY
Required
Software
Reliability
0.75 0.88 1.00 1.15 1.40 --
SCED
Required
Development
Schedule
1.23 1.08 1.00 1.04 1.10 --
STOR Main
Storage
Constraint
-- -- 1.00 1.06 1.21 1.56
TIME
Execution
Time
Constraint
-- -- 1.00 1.11 1.30 1.66
TOOL Use of
Software
Tools
1.24 1.10 1.00 0.91 0.83 --
TURN
Computer
Turnaround
Time
-- 0.87 1.00 1.07 1.15 --
VEXP
Virtual
Machine
Experience
1.21 1.10 1.00 0.90 -- --
VIRT Virtual
Machine
Volatility
-- 0.87 1.00 1.15 1.30 --
Example:
If your project is rated Very High for Complexity (Effort Multiplier of 1.30), and Low for Tools
Use (Effort Multiplier of 1.10), and all of the other cost drivers are rated to be Nominal, these
Effort Multipliers are used to calculate the Effort Adjustment Factor, which is used in the effort
equation:
21. EAF = 1.30 * 1.10 = 1.43
Effort = EAF * 3.2 * 31.05 = 14.5 SM
TDEV = 2.5 * 14.50.38 = 6.9 Months
Average staffing:
14.5 / 6.9 = 2.1 people
There are two reasons why Intermediate model produces better results than the Basic Model. First,
It considers the effect of more cost drivers. Second, in the Intermediate mode the system can be
divided into "components". DSI value and Cost Drivers can be chosen for individual components,
instead of for the system as a whole.COCOMO can estimate the staffing, cost, and duration of
each of the components--allowing you to experiment with different development strategies, to find
the plan that best suits your needs and resources.
Practical No. 5 : Class diagram using StarUML
Practical No. 6 : Use Case diagram using StarUML
Use case Modelling I
Aim: To Analyse the below text and then draw a use case diagram using an UML modelling
tool such as StarUML.
22. The following is a narrative description of the business process of organisation of
conferences with regards to the submitting, reviewing and accepting papers.
The author completes an online form that requests the user to input author name,
correspondence address, email and, title of paper. The system validates this data and, if
correct, asks the author to submit the paper. The author then browses to find the correct
paper on their system and submits it. Once received and stored, the system returns to the
author a reference number for the paper. Authors may submit as many papers as they like
to be considered for acceptance to the conference up until the deadline date for
submissions. Papers are allocated to referees for assessment. They review each paper and
submit to the system their decision. Once the programme organiser has agreed the
decisions authors are informed by email. Accepted papers are then schedule to be
delivered at a conference. This involves allocating a date, time and place for the
presentation of the paper.
Solution:
Practical No. 7 : Acitvity description for the project
Activity Diagram for the prepared Usecase Modelling
Aim : Derive an activity diagram from the narrative text by following the steps outlined
below.
System
Author
Submit Paper
Allocate Referee
Review Paper
Decide Acceptance
Set Program
Program Chair
Reviewer
Fill in author info
Upload file
<<include>>
<<include>>
Download file
<<include>>
Submit review report
<<include>>
Inform author
<<include>>
23. o Translate the above narrative text into an activity list. An activity list consists of a
sequences of short sentences in the form of
name + verb + noun [+ condition],
where the condition is optional. Such sentences are called activities. For example, the
following is an activity.
‘the author completes an online form’.
1. Transform each activity in the list into an activity/action node of the activity
diagram;
2. Identify the actors involved in the business process, and associate the actors
to each action/activity node;
3. Identify the sequential execution order, parallelism/concurrency and
synchronisation as well between the actions/activities, and draw the control
flows between the action/activity nodes, add synchronisation bar as
necessary;
4. Draw a swimlane for each actor and place the action/activity nodes in
appropriate swimlane;
5. Identify the objects passed between the activities, and add object nodes and
object flows into the diagram.
Solution:
• The activity list is given below.
a) The system requests the user to input author name, correspondence address,
email and, title of paper if the date is before the deadline.
b) The author completes an online form that contains the data.
c) The system validates this data.
d) The system asks the author to submit the paper, if the data is correct.
e) The author browses his system.
f) The author finds the correct paper on his system.
g) The author submits the paper.
h) The system receives the paper.
i) The system stores the paper.
j) The system assigns a reference number for the paper.
k) The system returns the reference number to the author.
l) The author goes back to activity 4) if they want to submit another paper.
m) System allocates papers to referees for assessment.
n) Referee reviews each paper.
o) Referee submits his assessments to the system.
p) The programme organiser make decisions on each paper’s acceptance.
q) The system emails the author of each paper of the decision.
r) The system creates a schedule for delivering accepted papers at a conference by
allocating a date, time and place for the presentation of each paper.
• The action/activity nodes are marked on the activity list as bold font.
• The actors are the name part of the activities.
• In this exercise, the actions are all sequentially ordered as in the activity list. The
parallelism and concurrency only occur in the form of different referees can perform their
reviews and assessments in parallel.
• The actors are:
24. (a) Author; (b) The system; (c) Referee; (d) Conference programme organiser;
• The objects involved in this process are:
(a) Online form; (b) paper; (c) paper’s reference number; (d) assessment report;
(e) Decision; (f) conference schedule.
25. Complete
online form
Request
user input
Validate
online form
Ask for
submissionBrowse
system
Find paper
Submit
paper
Receive
paper
Store paper
Assign
reference
number
Return
reference
number
Allocate to
referee
Review
paper
Submit
assessment
Make
decision
Email
decision
Create
schedule
Online form
Online form
Paper
Reference
number
Paper
Assessment
report
Decisions
Schedule
Author
System
Referee
Organiser
More
paper
26. Practical No. 8 : Activity description and diagram for the project
Use case document for a project
Aim : TO draw the activity diagram for the given problem of Use case
Solution :
The following is a use case description of the examination paper preparation support system.
Draw a UML activity diagram according to the description.
Use case name: submit question
Participant: lecturer
Entry conditions:
1. The question is ready and stored in a file
2. The lecturer is assigned to the module
Exit conditions:
1. The file is uploaded to the system
2. The module leader is notified of the availability of the question
3. The event is logged by the system
Flow of Events:
1. The lecturer logs into the system by entering his/her username and password;
2. The system checks the username and password;
3. The system displays the list of modules of which he/she is the lecturer, module leader
and/or internal examiner;
4. The lecturer selects a module and his/her role in the module as a lecturer;
5. The system prompts the user to enter the file name and location on his/her computer, and
additional information if any;
6. The lecturer enters file name and location, and types in the additional information;
7. The lecturer submits the questions and the file is uploaded to the system;
8. The system saves the file;
9. The system confirms the success of uploading the file.
10. The system notifies the module leader of the submission of the questions.
Exceptional conditions and alternative flow of events:
When the username and password is not correct:
3.1: display error message, go back to step 1;
When the lecturer is not listed on the module:
4.1: quit the system;
Special requirements:
1. The file should be encrypted when transmitted from lecturer’s computer to the server
2. The notification of success in uploading the file should be within 20 seconds
3. The event should be recorded in a log file to contain the following information:
a) name of the lecturer,
b) date and time of the event,
c) the name of the event (upload exam question),
d) the file on the server that stores the questions.
27. Solution:
Practical No. 9 : Work Breakdown Structure for the given Project
Aim : Create a Work Breakdown Structure
Lecturer
System
login check login password[username and password]
display module list
select module and role prompt input file id
input file id and info
upload file and info confirm upload success
notify module leader
display error message[module list]
[file and info]
[model and role] save file and info