30-05-2011, 08:35 AM
INTRODUCTION
1.1.1 OBJECTIVE
To be an Indian multinational engineering enterprise providing total business solution through quality product, system and services in the field of energy, industry, transportation, infrastructure and other potential areas.
1.1.2 ABOUT BHEL
BHEL is the largest engineering and manufacturing enterprise in India in the energy-related/infrastructure sector, today. BHEL was established in earlier 50’s, ushering in the indigenous Heavy Electrical Equipment industry in India - a dream that has been more than realized with a well-recognized track record of performance. The company has been earning profits continuously since 1971-72 and paying dividends since 1976-77.
BHEL manufactures over 180 products under 30 major product groups and caters to core sectors of the Indian Economy viz., Power Generation & Transmission, Industry, Transportation, Telecommunication, Renewable Energy etc. The wide network of BHEL has 14 manufacturing divisions, four Power Sector regional centre, over 100 project sites, eight service centre and 18 regional offices, enables the Company to promptly serve its customers and provide them with suitable products, systems and services -- efficiently and at competitive prices. The high level of quality & reliability of its products is due to the emphasis on design, engineering and manufacturing to international standards by acquiring and adapting some of the best technologies from leading companies in the world, together with technologies developed in its own R&D centre.
BHEL has acquired certifications to Quality Management Systems (ISO 9001), Environmental Management Systems (ISO 14001) and Occupational Health & Safety
Management Systems (OHSMS 18001) and is also well on its journey towards Total Quality Management.
BHEL has:
Installed equipment for over 90,000 MW of power generation -- for Utilities, Captive and Industrial users.
Supplied over 2,25,000 MVA transformer capacity and other equipment operating in Transmission & Distribution network up to 400 kV (AC & DC).
Supplied over 25,000 Motors with Drive Control System to Power projects, Petrochemicals, Refineries, Steel, Aluminum, Fertilizer, Cement plants, etc.
Supplied Traction electrics and AC/DC locos to power over 12,000 kms Railway network.
BHEL's operations are organized around three business sectors, namely Power, Industry - including Transmission, Transportation, Telecommunication & Renewable Energy - and Overseas Business. This enables BHEL to have a strong customer orientation, to be sensitive to his needs and respond quickly to the changes in the market.
BHEL's vision is to become a world-class engineering enterprise, committed to enhancing stakeholder value. The company is striving to give shape to its aspirations and fulfill the expectations of the country to become a global player.
The greatest strength of BHEL is its highly skilled and committed 43,500 employees. Every employee is given an equal opportunity to develop himself and grow in his career. Continuous training and retraining, career planning, a positive work culture and participative style of management – all these have engendered development of a committed and motivated workforce setting new benchmarks in terms of productivity, quality and responsiveness.
1.2 OVERVIEW OF THE PROJECT:
The project “Fixed Tenure Appointee’s Leave Management System” is based on the automation of leave/absence assessment and maintenance of the record related to leave earned by the Fixed Tenure Appointee (FTA) time to time during their working days. This is a stand-alone application and used by only a single person who is the authorized to deal with this application. The assessment of leave/absence business is on the basis of a rule stated by the company for them. The each appointee will be given one-day leave after completion of twenty days cycle. These leaves will be carry forwarded if not going to earned and will got clubbed with the next one-day usual leave after the completion of the next twenty days cycle. There are also some pre-declared holidays included in the twenty days working cycle, by the company and other usual holidays like Sunday /Second Saturday/last Saturday of the month as well, no matter. There is also a rule regarding the availing of one-day leave to FTA’s. If an appointee is absent for more than ten days, no matter how much leaves are in his hand, will not given a one-day availed leave after entitlement.
In order to assess the leave/absence, the monthly absentee report of the appointee’s is supposed to be submitted by the each department at the end of the each month to the Human Resource department and then the application user (there is single user only) is supposed to perform some data feeding task (absentee statement of each department’s appointee’s). The automated system is now able to perform the entire task itself.
This software application is performing many functions such as Adding, Viewing, Editing of records and absentee statement posting for the each appointee of a particular department. We are also managing the year planner, which contains all the ten pre-declared holidays. The purpose of maintaining these dates whether these are lies in the leave domain of appointee, if yes then not to consider.
This computerized application frees the existing system from the bundles of files and stock of papers and a lot of pain to calculate the twenty-day cycle date from their date of joining then also keep the record of the leave/absence well.
2: SOFTWARE ENGINEERING PARADIGM APPLIED
To solve actual problem in an industry, software engineer or a team of engineers must incorporate a development strategy that encompasses the process, methods and tools layers. This strategy is often referred to as a process model or a software model paradigm. A process model for software engineering is chosen based on nature of project an application, the methods and tools to be used and the controls and the deliverables that are required.
There are a variety of different process model for software engineering. Each represents an attempt to bring order to an inherently chaotic activity. It is important to remember that of the model has been characterized in away that assist in the control in the coordination of the real software project.
The model use for this project is linear sequential model. Some times called the classic life cycle or the waterfall model, the linear sequential model suggests a systemic, sequential approach to software development that begins at the system level and progressive through the analysis, design, coding, testing and support.
System/ Information
Engineering
Analysis Design Code Test
Modifying after a conventional engineering cycle, the linear sequential model encompasses the following activities:
System/ Information engineering and modeling: because software is always part of larger system, work begins by establishing requirement for all system elements and then allocating some subsystem of these requirements to software. This system view is essential when software must interact with other elements such as hardware, people, and databases. System engineering and analysis encompasses requirement gathering at the system level when a small amount of top level design and analysis. Information engineering encompasses requirements gathering at the strategic business level and at the business area level.
Software Requirement Analysis: The requirement gathering process is focused specially on software. To understand the nature of the program to be building, the software engineer (“Analyst”) must understand the information domain for the software, as well as required functions behavior, performance and interface. Requirements for both the system and the software are documented and reviewed with the customer.
Design: Software design is actually a multi step process that focuses on four districts attributes of the program: data structure, software architecture, interface representation and algorithmic detail. The process translate requirement into a representation of the software that can be assessed for quality before coding begins. Like requirements, the design is a documented and becomes part of the software configuration.
Code Generation: The design must be translated into a machine-readable form. The code generation step performs this task. If design is performed in a detailed manner, code generation can be accomplished mechanistically.
Testing: Once code has been generated, program testing begins. The testing process focuses on the internal logic of the software, ensuring that all statement has been tested, and on the
External function; i.e. conducting test to uncover errors and ensure that define input will produce actual results that agree with required.
Support: Software will undoubtedly undergo change after if is delivered to the customer. Change will occur because errors have been encountered, because the software must be adopted to accommodate changes in its external environment, because the customer requires functional or performance enhancements. Software supports/Maintenance reapplies each of the preceding phases to an existing program rather then a new one.
Drawbacks: The linear sequential model is the oldest and the most widely used paradigm for software engineering. However, criticism of the paradigm has cost even active supports to question its efficiency. Among the problems that are some times encountered when the linear sequential model is applied are:
1) Real projects rarely follow the sequential flow that the model proposed although the linear model can accommodate iteration, it does so indirectly. As a result, changes can cause confusion as the project team proceeds.
2) It is often difficult for the customer to state all requirements explicitly. The linear sequential model required this and has difficulty accommodating the natural uncertainly that exists at the beginning of many projects.
3) The customer must have patience. A working version of program will not be available until late in the project time-span. A major blunder undetected until the working program is reviewed, can be disastrous.
The linear nature of the classic life cycle leads to “blocking states” in which some project team members must wait for other members of the team to complete dependent task. In fact, the time spent waiting can exceed the time spent on productive work. The blocking state tends to be more prevalent at the beginning and end of a linear sequential process
SYSTEM ANALYSIS
Analysis is a method that examines the requirements from the perspective of the class and object found in the vocabulary of the problem domain. Analysis is concerned with devising a precise, concise understandable and correct model of the real world. Development of software is quite similar to construction of a building both requires understanding of the requirements and the real-world environment in which it will exist. The objective in the models should be application domain concept and not computer implementation concepts such as data structures .It is related with "what" of the desired system i.e. with the purpose of the system. Analysis model should not contain any implementation details for e.g. a class window in a workstation windowing system would be described in terms of the attributes and operation visible to a user.
The purpose of analysis is to model the real-world system so that it can be understood, for this the requirement must be examined, their implementation must be analyzed and finally they must be restated. The result of analysis is to understand the problem as a preparation for design.
Get the full report here:
http://www.4shareddocument/GaboKGJg/Fina...Report.htm
1.1.1 OBJECTIVE
To be an Indian multinational engineering enterprise providing total business solution through quality product, system and services in the field of energy, industry, transportation, infrastructure and other potential areas.
1.1.2 ABOUT BHEL
BHEL is the largest engineering and manufacturing enterprise in India in the energy-related/infrastructure sector, today. BHEL was established in earlier 50’s, ushering in the indigenous Heavy Electrical Equipment industry in India - a dream that has been more than realized with a well-recognized track record of performance. The company has been earning profits continuously since 1971-72 and paying dividends since 1976-77.
BHEL manufactures over 180 products under 30 major product groups and caters to core sectors of the Indian Economy viz., Power Generation & Transmission, Industry, Transportation, Telecommunication, Renewable Energy etc. The wide network of BHEL has 14 manufacturing divisions, four Power Sector regional centre, over 100 project sites, eight service centre and 18 regional offices, enables the Company to promptly serve its customers and provide them with suitable products, systems and services -- efficiently and at competitive prices. The high level of quality & reliability of its products is due to the emphasis on design, engineering and manufacturing to international standards by acquiring and adapting some of the best technologies from leading companies in the world, together with technologies developed in its own R&D centre.
BHEL has acquired certifications to Quality Management Systems (ISO 9001), Environmental Management Systems (ISO 14001) and Occupational Health & Safety
Management Systems (OHSMS 18001) and is also well on its journey towards Total Quality Management.
BHEL has:
Installed equipment for over 90,000 MW of power generation -- for Utilities, Captive and Industrial users.
Supplied over 2,25,000 MVA transformer capacity and other equipment operating in Transmission & Distribution network up to 400 kV (AC & DC).
Supplied over 25,000 Motors with Drive Control System to Power projects, Petrochemicals, Refineries, Steel, Aluminum, Fertilizer, Cement plants, etc.
Supplied Traction electrics and AC/DC locos to power over 12,000 kms Railway network.
BHEL's operations are organized around three business sectors, namely Power, Industry - including Transmission, Transportation, Telecommunication & Renewable Energy - and Overseas Business. This enables BHEL to have a strong customer orientation, to be sensitive to his needs and respond quickly to the changes in the market.
BHEL's vision is to become a world-class engineering enterprise, committed to enhancing stakeholder value. The company is striving to give shape to its aspirations and fulfill the expectations of the country to become a global player.
The greatest strength of BHEL is its highly skilled and committed 43,500 employees. Every employee is given an equal opportunity to develop himself and grow in his career. Continuous training and retraining, career planning, a positive work culture and participative style of management – all these have engendered development of a committed and motivated workforce setting new benchmarks in terms of productivity, quality and responsiveness.
1.2 OVERVIEW OF THE PROJECT:
The project “Fixed Tenure Appointee’s Leave Management System” is based on the automation of leave/absence assessment and maintenance of the record related to leave earned by the Fixed Tenure Appointee (FTA) time to time during their working days. This is a stand-alone application and used by only a single person who is the authorized to deal with this application. The assessment of leave/absence business is on the basis of a rule stated by the company for them. The each appointee will be given one-day leave after completion of twenty days cycle. These leaves will be carry forwarded if not going to earned and will got clubbed with the next one-day usual leave after the completion of the next twenty days cycle. There are also some pre-declared holidays included in the twenty days working cycle, by the company and other usual holidays like Sunday /Second Saturday/last Saturday of the month as well, no matter. There is also a rule regarding the availing of one-day leave to FTA’s. If an appointee is absent for more than ten days, no matter how much leaves are in his hand, will not given a one-day availed leave after entitlement.
In order to assess the leave/absence, the monthly absentee report of the appointee’s is supposed to be submitted by the each department at the end of the each month to the Human Resource department and then the application user (there is single user only) is supposed to perform some data feeding task (absentee statement of each department’s appointee’s). The automated system is now able to perform the entire task itself.
This software application is performing many functions such as Adding, Viewing, Editing of records and absentee statement posting for the each appointee of a particular department. We are also managing the year planner, which contains all the ten pre-declared holidays. The purpose of maintaining these dates whether these are lies in the leave domain of appointee, if yes then not to consider.
This computerized application frees the existing system from the bundles of files and stock of papers and a lot of pain to calculate the twenty-day cycle date from their date of joining then also keep the record of the leave/absence well.
2: SOFTWARE ENGINEERING PARADIGM APPLIED
To solve actual problem in an industry, software engineer or a team of engineers must incorporate a development strategy that encompasses the process, methods and tools layers. This strategy is often referred to as a process model or a software model paradigm. A process model for software engineering is chosen based on nature of project an application, the methods and tools to be used and the controls and the deliverables that are required.
There are a variety of different process model for software engineering. Each represents an attempt to bring order to an inherently chaotic activity. It is important to remember that of the model has been characterized in away that assist in the control in the coordination of the real software project.
The model use for this project is linear sequential model. Some times called the classic life cycle or the waterfall model, the linear sequential model suggests a systemic, sequential approach to software development that begins at the system level and progressive through the analysis, design, coding, testing and support.
System/ Information
Engineering
Analysis Design Code Test
Modifying after a conventional engineering cycle, the linear sequential model encompasses the following activities:
System/ Information engineering and modeling: because software is always part of larger system, work begins by establishing requirement for all system elements and then allocating some subsystem of these requirements to software. This system view is essential when software must interact with other elements such as hardware, people, and databases. System engineering and analysis encompasses requirement gathering at the system level when a small amount of top level design and analysis. Information engineering encompasses requirements gathering at the strategic business level and at the business area level.
Software Requirement Analysis: The requirement gathering process is focused specially on software. To understand the nature of the program to be building, the software engineer (“Analyst”) must understand the information domain for the software, as well as required functions behavior, performance and interface. Requirements for both the system and the software are documented and reviewed with the customer.
Design: Software design is actually a multi step process that focuses on four districts attributes of the program: data structure, software architecture, interface representation and algorithmic detail. The process translate requirement into a representation of the software that can be assessed for quality before coding begins. Like requirements, the design is a documented and becomes part of the software configuration.
Code Generation: The design must be translated into a machine-readable form. The code generation step performs this task. If design is performed in a detailed manner, code generation can be accomplished mechanistically.
Testing: Once code has been generated, program testing begins. The testing process focuses on the internal logic of the software, ensuring that all statement has been tested, and on the
External function; i.e. conducting test to uncover errors and ensure that define input will produce actual results that agree with required.
Support: Software will undoubtedly undergo change after if is delivered to the customer. Change will occur because errors have been encountered, because the software must be adopted to accommodate changes in its external environment, because the customer requires functional or performance enhancements. Software supports/Maintenance reapplies each of the preceding phases to an existing program rather then a new one.
Drawbacks: The linear sequential model is the oldest and the most widely used paradigm for software engineering. However, criticism of the paradigm has cost even active supports to question its efficiency. Among the problems that are some times encountered when the linear sequential model is applied are:
1) Real projects rarely follow the sequential flow that the model proposed although the linear model can accommodate iteration, it does so indirectly. As a result, changes can cause confusion as the project team proceeds.
2) It is often difficult for the customer to state all requirements explicitly. The linear sequential model required this and has difficulty accommodating the natural uncertainly that exists at the beginning of many projects.
3) The customer must have patience. A working version of program will not be available until late in the project time-span. A major blunder undetected until the working program is reviewed, can be disastrous.
The linear nature of the classic life cycle leads to “blocking states” in which some project team members must wait for other members of the team to complete dependent task. In fact, the time spent waiting can exceed the time spent on productive work. The blocking state tends to be more prevalent at the beginning and end of a linear sequential process
SYSTEM ANALYSIS
Analysis is a method that examines the requirements from the perspective of the class and object found in the vocabulary of the problem domain. Analysis is concerned with devising a precise, concise understandable and correct model of the real world. Development of software is quite similar to construction of a building both requires understanding of the requirements and the real-world environment in which it will exist. The objective in the models should be application domain concept and not computer implementation concepts such as data structures .It is related with "what" of the desired system i.e. with the purpose of the system. Analysis model should not contain any implementation details for e.g. a class window in a workstation windowing system would be described in terms of the attributes and operation visible to a user.
The purpose of analysis is to model the real-world system so that it can be understood, for this the requirement must be examined, their implementation must be analyzed and finally they must be restated. The result of analysis is to understand the problem as a preparation for design.
Get the full report here:
http://www.4shareddocument/GaboKGJg/Fina...Report.htm