5.Comp sci..Experimental FULL

International Journal of Computer Science Engineering and Information Technology Research (IJCSEITR) ISSN 2249-6831 Vol.2, Issue 4, Dec 2012 45-52 Š TJPRC Pvt. Ltd.,

EXPERIMENTAL REPORT TO ANALYSE HUMAN THOUGHTS ON SOFTWARE ENGINEERING 1 1, 2 3

PRAKRIT TRIVEDI, 2ANIL KUMAR DUBEY & 3 VIPUL SHARMA

Asst. Prof. (CSE & IT Department), Govt. Engineering College Ajmer-305001, Member IEEE, India

Faculty CSE Department, Govt. Engineering College Ajmer-305001, Rajasthan Technical University- Kota, Rajasthan, India

ABSTRACT Software engineering is the area of energizing where an engineer collects the physical fundamentals of a given concept through a scientist and perform practical on it, to check its overall processing and to verify it.

In software

engineering, researchers have given the physical fundamentals for performing something and these fundamental concepts are verified by an engineer. After this process an engineer has a heavy bundle of experimental data. They use few proposal models & techniques to analysis the overall work. Finally the team of technologists develop the product for people.

Therefore we can say that range of work for these three people are bound to each other but not common. This paper has three different phases of current analysis to enlighten the mind of employees and researchers.

In the first phase of the paper we clear the concept of scientist, engineer and technologist. In the second phase we analyse the age of software and prove that software does not have age limit and last phase of the paper shows graphical results of the survey to distinguish between techniques, method and approach. In this paper we have also highlighted the impact of v& v on software engineering.

KEYWORDS: SE, Re, Technologist, Research, V & V PHASE I: SET Introduction Currently 10 % people are either engineers or pursuing graduate course in engineering, 40 % are science graduates and so on. Mostly people are working in software industry. According to survey, 50% of them don’t know the differences among these three positions (which is co-ordinated by industry for that particular organization) i.e., of scientist, engineers and technologists. Here we introduce student and employee about their position and work needed by them.

Earlier people thought of becoming just science graduates. After few years, engineering diploma followed by degrees was started. Software engineering often works in conjunction will another discipline i.e., SE with AI for automation; SE with image processing for research.

Different Cases ON SE In table 1, it is clarified that the work of a scientist is the initialization of the new thoughts to do something, and they are also involve in perform reasoning.

46

Prakrit Trivedi, Anil Kumar Dubey & Vipul Sharma

Table 1: Differences among Scientists, Engineer and Technologies on the Basis of their Work S.No 1 2

Scientist Provide the physical fundamental Proposes new models

3

Engineer Verify and validate statement of scientist Checks status of proposed model with current industry standards Confirms the problem

Technologist Deliver the final product Provides availability of the model to market

Searches problems in Exposes the problem testing 4 Concepts of product Performs action on it ( but lot Develop new product from maintenance of meta data are needed) collected meta data.

5 Discover invent Develop, final shape Final shape to market In the second phase the engineer performs experiments on the concept and gives final shape to design of the product. Based on engineer’s analytical study, the technologist checks the applicability of the project to the market and conforming the final design.

Important Attributes According to the latest technology in Software engineering there are a lot of attributes affecting the development process. Major attributes are as given below:1.

Understanding the basic technology.

2.

Interaction of theoretical concepts & application environment.

3.

Classifying the work.

4.

Psychological up liftmen of employees.

5.

Improving each employee’s working fundaments.

No Similar 8% All Similar 7% Engg & Scientist 18%

Survey on similarity of Scientist, Engineer & Engg & Technologist Tech

Tech & Scientist 28%

Engg & Tech 39%

Tech & Scientist

Figure 1: Graphical Result of Analytical Survey on Scientists, Engineer and Technologies

PHASE II: SOFTWARE AGE Introduction This is a conceptual question for every software organization. Most of them don’t know about it. But, if you are a customer, want to buy/use software, and then it is necessary for you that have knowledge of this question. The marketing survey shows that 70 percent people did not know the age limit of software. Few thought that software had age but did not have the reason for the same. The survey for the same was also

performed on engineering students. We did the literal on

47

Experimental Report to Analyse Human Thoughts on Software Engineering

150 students (131 of them offline and 19 online) and found out that only 53 students gave the response that software did not have the age limit.

The chart shows below that, more than 50 % people did not know the actual concept about the age limit of software. They thought software will wear out with time. They gave the simple example that some software was mostly used in earlier days, but now a-days it is not uses.

80 70 60 50

Yes

40

No

30

Don’t know

20 10 0 views on software age

Figure 2: Graphical Result of Survey on Software Age This was sufficient and appropriate reason for them. As per the survey 14 % people use software daily for their respective work but they did not have idea about the age limit of software. Except those people, remaining 34 % were satisfied that software does not have age limit i.e., it does not wear out with time.

Prove L1: As we all are using electronic & mechanical system in our everyday life. We see that mobile phones, calculators etc do not work as efficiently as they did 5-10 years back or they do not have newer facilities. Same is the case with cars/automobiles. But with software, after using it for few years’ bugs might come or requirements might change which can be fixed/accommodated.

Figure 3: Bathtub Curves for Software Reliability [3] L2: According to the bathtub curve of software reliability: when the useful lifecycle of software starts it works propped. After little time duration due to internal error software might not work properly. Tester removes the error and upgrades it application use. This process may be done many times. After few time periods our software is corrected and

48

Prakrit Trivedi, Anil Kumar Dubey & Vipul Sharma

work continuously without break i.e., we can say that software will not expire with time period. Hence there is no age limit of software.

PHASE III: TMA Introduction TMA stands for techniques, methods, and approaches. By using techniques, methods, we can solve the upcoming problems in our system. We also apply few important approaches for solving these problems. Here we classify them with appropriate definitions: (i) Approaches:- By using appropriate approaches we select a particular model, to predict the software for failure & faults. Two important approaches are (a) A model selection approach. (b) Systematic approach of modelling.

Approaches

Methods

Techniques Figure 4: Inter-Relativity of TMA

Figure 4: Inter-Relativity of TMA

Few approaches are proposed to solve the software engineering problem. Different researchers proposed different approach to study and analyse software. (ii)

Techniques: - There are many techniques used in computer science for searching the problem, its location and

authentication. Software Testing Techniques/Practices [9]

(iii )

째

Black Box/UAT

째

Exploratory

째

Unit/Developer/White Box

Methods: - By the help of methods we are establishing approaches and techniques. It means they are inter-related

to each other. G.J. Knafl (1993) gave the systematic approach to software reliability model by a methodology [4].

49

Experimental Report to Analyse Human Thoughts on Software Engineering

Survey on techniques, methods, and approaches Techniques and methods are same things

Method and approaches are same things

Techniques and approaches are same things Techniques and approaches are same things, 28

Techniques, methods, and approaches are same All are things, 28 different, 18

Techniques, methods, a nd approaches are same things

Other, 25 All Similar

All Similar, 7 Method and approaches are same things, 49

Techniques and methods are same things, 20

All are different

Figure 5: Pie Chart of survey on TMA

PHASE IV: V & V Introduction Verification and validation are two important terms used to check the status of project for upcoming queries.

These queries are such that, whether the project is fulfilling the required criteria of customer and satisfying him at a higher percentile. Basically these two terms are coming at the end of the project.

V&V technique uses different testing methods in different positions. The IEEE Standard for Software Verification and Validation (IEEE Std 1012-1998) contains information on software integrity levels, the V & V process, the Software V & V reporting, administrative, documentation requirements, an outline of the software verification and validation plan [5].

50

Prakrit Trivedi, Anil Kumar Dubey & Vipul Sharma

Verification Different organizations have given different definitions of the verification. We also propose a definition of verification on the basis of our experience that is “verification is the process of confirmation that the upcoming output is expected according to the input”. During the Verification, the work product (the ready part of the Software being developed and various documentations) is reviewed/examined personally by one or more persons in order to find and point out the defects in it. This process helps in prevention of potential bugs, which may cause the failure of project [8]. The process of verification confirms that the bugs did not transfer to the next phase from previous.

Validation We also propose the definition of validation as “validation is the process to produce the desire result”. Simply we can say that “validation is the process for checking the status of outputs and clarifying that the upcoming output is valid or not in prospect of user’s exception”. The validation process ensures that the output is acceptable to the user. When the verification process is completed, the next process validation is ready for processing of each of the activities performed by verification process corresponding to validation activity. V & V process improves the quality of software and detects error as soon as possible.

Remarking On V & V The searching of faults is the process of Verification technique where we use the guessing process such as neural networks of problem searching. If the developing project is verifying and validates the upcoming output performance, it means its reliability is nearly 60 percentile. Fault is an unstrapped error which can change the performance of the program.

If the developed software does not give the output as required then there may be a fault. Due to the presence of these faults system may fail [6]. V&V need additional cost; nearly 25% of project development and it also requires the extra burden of work in documentation and meeting charges. The development process of any software follows some testing techniques and verifies the implementation with user’s required specifications. In earlier days the v& v process was handled by the software engineers but now-a-days software has become so complex that can’t be handled by the software engineer alone.

It requires a specific team which needs a lot of cost to verify and validate the status of software. Due to the complexity, V&V need nearly 20 to 30% amount of project development cost and more to provide confidentiality about the correct result.

During the verification and validation process we remove such problems. It means V&V process improves the percentages of reliability of software. V & V is a time consuming process. It takes 25-30% of project cost. After completion of V&V process, errors and bugs are detected and removal takes place. It means our software is reliable for future work.

Failure occurs due to the presence of bugs, errors, defects and faults. During the verification and validation process we remove these things. It means V&V process improve the percentages of reliability of a software. Finally we can say that V&V put a better impact on software reliability.

PHASE V: CONCLUSIONS Finally we say that employees and students should understand their place and job in the industry and differentiate it with non software professionals. In the end the distinction between technique, methods and approaches and then impact on people’s mind was discussed. V & V is time consuming process. It takes 25-30% of project amount.

Experimental Report to Analyse Human Thoughts on Software Engineering

51

REFERENCES 1.

[QSPM 08] R.T.Futrell, D.F. Shafer and L.T. Shafer, Quality Software Project Management, fifth Impression, 2008.

2.

“Software Engineering” by Roger S.Pressmen, 6th edition.

3.

John D. Musa “Introduction to Software Reliability Engineering and Testing” Proceedings on the 8th International Symposium on Software Reliability Engineering, IEEE 1997.

4.

A thesis on “Software Reliability Model Study” by Michael Grottke in PETS 2001.

5.

Effect of Software Verification and Validation on Projects by buzzle.com.

6.

Verification/Validation/Certification, Carnegie Mellon University 18-849b Dependable Embedded Systems, Spring 1999, Author: Eushiuan Tran.

7.

[Andriole86] Andriole, Stephen J., editor, Software Validation, Verification, Testing, and Documentation, Princeton, NJ: Petrocelli Books, 1986.

8.

"An introduction to ‘Verification & Validation Model’ used in improvement of software project development life cycle", Software Verification & Validation Model - An Introduction by buzzle.com.

9.

http://www.perftestplus.com/resources/approaches_ppt.pdf

Bibliography of authors Ms. Prakriti Trivedi (Asst. Professor.) received his BE (Computer Science & Engineering.) from MBM Engineering College Jodhpur in 1994. ME (Computer Science & Engineering.) from NITTTR, Punjab University, Chandigarh, India; She has more than 15+ years’ teaching experience (from Aug 1995). She is presently working as Asst. Professor (Department- CS & IT) in Govt. Engineering. College Ajmer. She has several papers published in international & national journal/conferences. She is also responsible person in different administrative department and giving guidance to major projects of B. Tech students. She is also the guide of more than 10 students of M. Tech thesis. She is also organised many national conferences and workshop.

Anil Kumar Dubey has received his B. Tech degree in Information Technology, from GNIT Greater Noida (UP Technical University- Lucknow) and M. Tech from Govt. Engineering College Ajmer (Rajasthan Technical University- Kota), Currently working as Asst. Professor (Contractual basis) in CSE department at Govt.

Engineering College Ajmer. He has presenting several papers in international & national conferences. Her presented paper is indexes in reputed journals and several digital libraries like IEEE. His research interests include software reliability, software construction, software reuse, Soft computing, HPSC & SCM. He as Reviewer Committee member of many international journals (like Springer, Elsevier etc) and international Conferences (like IEEE, ACM etc) and Review 10 research papers allotted editor board. He is member of various technical research societies such as IEEE Computer Society, Computer Society of India & ISTE etc.

Vipul Sharma has received his B.E degree in CSE (Computer Science & Engineering) from Government Engineering College Ajmer affiliated to University of Rajasthan. He is currently working as a Faculty in CSE department of Govt. Engineering College; Ajmer. His research interest includes DBMS (Database Management Systems), SE (Software Engineering).