Framework for Domain Analysis of Teleteaching System: A Semiformal Approach Animesh Dutta #1 , Imon Banerjee #2 , Shrutilipi Bhattacharjee #3 , Ranjan Dasgupta 4 , Swapan Bhattacharya 5 # Dept. of IT , NIT. Durgapur, India, 4 Dept of CSE, NITTTR, Kolkata, India, 5 Dept of CSE, NIT Durgapur, India 1 animeshrec@gmail.com , 2 imonban@gmail.com, 3 shrutilipi.2007@gmail.com 4 ranjandasgupta@hotmail.com , 5 bswapan2000@yahoo.co.in Abstract- Understanding user requirement is an integral part of information system design and is critical to the success of interactive systems. It is now widely understood that successful systems and products begin with a clear understanding the domain of the system, and needs and requirements of the users. There are several purposes for modeling and analyzing the problem domain before starting the software requirement analysis. First it focuses on the problem domain so that the domain users could be involved easily. Secondly a comprehensive description on the problem domain will advantage getting a comprehensive software requirement model. This paper model an ontology based framework to satisfy the criteria mainly organizational structure, agent’s interaction, goal achievement. In this paper we show a very popular interactive system “Teleteaching” as the case study for the proposed framework. Keywords- Ontology, Conceptualization, Teleteaching, Domain Analysis, Requiremnet Engineering. 1 Introduction Several surveys indicate that a significant percentage of software fail to meet business objectives or are outright failure. One of the reasons for this is that domain and requirement analysis is typically overlooked in real life software projects. Good requirement practices can accelerate software development. The process of defining business requirements aligns the stakeholders with shared vision, goals and expectations. Substantial user involvement in establishing and managing changes to agree upon requirements increases the accuracy of requirements, ensuring that the functionality built will enable users to perform essential business tasks. Software requirement engineering encompasses the two major sub domains of requirement definition and requirement management: Requirement definition is the collaborative process of collecting, documenting and validating a set of requirements that constitute an agreement among key project stakeholders. Requirements definition is further subdivided into the critical process areas of elicitation, analysis, specification and validation process. From a pragmatic perspective, requirement definition strives for requirements that are user validated and clear enough to allow the team to proceed with design, construction and testing at an acceptable level of risks. Requirement management involves working with a defined set of product requirements throughout the product’s development process and its operational life. It also includes managing changes to that set of requirements throughout the project lifecycle. An effective requirement definition and management solution creates accurate and complete system requirements while helping organization communications is an effort to better align IT with business needs and objectives. The paradigm shifts from mainframes in the 1950s-1970s to the personal computer technology of the 1980s and the networked computing devices of the 2000s can be conceptually modeled by paradigm shifts from algorithms to sequential interaction and then to distributed (multiagent,collaborative) interaction. Interactive models provide a domain independent unifying view of the design space for software intensive systems. The key dimension of change in software-intensive systems is interactiveness. Whereas at one time computing was mostly batch the execution of algorithms, with all input data supplied a priori and all output generated afterword-today ongoing interaction is ubiquitous. This interaction differs semantically from iterated batch computing in that each computing entity maintains a persistent state that evolves and enables computations to be driven by their entire input/output histories. One popular application “Teleteaching” is fundamentally interactive and can not be properly understood until more research is done on domain-independent models and on the principles of interactions. The requirements of a software system are often ambiguous, incomplete, redundant and variant at the requirement analysis phase of a system. Requirement generated by different stakeholders may be inconsistent since different stakeholders and users may have different perspective on the system. This may bring about the same term is applied to different concepts and different terms are used to denote the same entity. A suitable solution was the use of ontology which can make sure that different designers have a common understanding of the term to be used. Ontology was originally concept from philosophy. It describes the essence and composition of the world, as said by the philosophers. In computer science, ontology is mainly used for knowledge representation and defining the concept of the system It provides a means for knowledge sharing which is very much necessary for large scale, complex real software projects. For the last few years more and more software engineers become interested in the research system designing using ontology concept [1]. The five points