Short Paper Proc. of Int. Conf.

on Advances in Computing, Control, and Telecommunication Technologies 2011

Development of Alternative to Pressman Standard on Small Solution Development, Case: Bina Nusantara Theses Student
Renan Prasta Jenie
1

Bina Nusantara Information Technology Directorate, Jakarta, Indonesia Email: RJenie@Binus.edu

AbstractResearch-Lab! Aim for developing real world applicable solution based on Student Theses and Internship. Problems arise when using Pressman Standard. We proposed several simple design notations in class as precursor to UML. The research aims to introduce the simplified diagram to research student, and to measure the effect of system implementation and difference in consistence of indexing, robustness, and overall development time. The proposed solution proved to alleviate indexing existence problem by correlation 0.65, consistence by 0.64, design duration by 0.72, but still not effective enough on robustness problem by 0.25. Change on how software engineering taught is imminent in Binus, aim to shift student paradigm from tools to system development. Further research needed to find alternatives on design methods for small project. Index Terms Software Engineering, UML Design Notation, Pressman, Small Solution Development, Small Enterprise.

They should use simplified modelling standard ([8] and [9]), as opposed to full UML modelling for Large Enterprise [10]. The system should address the rapidness aspect of development [11], as well as utilization of team and community based development [12]. B. Solution Technological Background Application development already shifting to community based development, condoned by the use of Open Source Solution (OSS). Use of Open Source Solution means adding several crowd utilization activities [13]. Developer could choose to follow OSS Utilization standards such as [14]. Development of ubiquitous system solution means the use of Component Based Software Engineering, means additional component evaluation phases [15]. Preferred solution architecture is Model View Controller [16]. Development of mobile solution means handling business, legal, and research aspects as well [17]. This problem is handled in separate research. Several Solutions for Mobile Development [7] and, in concept, Mixed Reality [18] such as Appcelerator [19] and Gitorious [20] already utilizing Social Solution as its capabilities [21]. Development of ubiquitous solution means developer must ascertain that the solution made address several rules (summarized from [7] and [5]). The system should be able to profile her stakeholders. The system should be able to grab the stakeholders context. The system should disseminate the information based on profile and context given. The dissemination should be made promptly upon creation, or on the pre defined time. C. Pressman Standard and UML Review [6] Pressman Standard state that developer should explain total 8 aspects in Analysis Phase and Design Phase, as in Figure 1. Scenario Design describe how to stakeholder interacting with the system, normally denoted using Use Case Diagram. Flow Design describes how messages and data are disseminated within or inter system, normally denoted using Data and Control Flow Diagram. Class Design describes system internal structure, normally denoted using Class Diagram. Behavioural Design describes the manners system acts based on environmental input, normally denoted using State and Sequence Diagram. Component Level Design describes the construction of its internal component, normally denoted as either black box, Pseudo codes, even designed as separate solution. 123

I. INTRODUCTION A. Software Engineering Background Student Advisory System is part of Job Description of Lecturer. Here, in Bina Nusantara University, Research-Lab! [1] Aim for developing real world applicable solution based on Student Theses and Internship. This program made to meet the business world demand for entrepreneur or employable professional [2] [3]. To address the needs, Education made should address capabilities needed for typical software engineering job position [4]. In Binus University, a student research team consist of 1 to 3 research students and 1 to several advisory lecturers, qualified to be called Very Small Enterprise. Most of research is in applied software engineering. Mostly, they develop a ubiquitous system solution [5] using Waterfall Model Process, UML 2.0 Notation, and Pressman Software Development Standard [6]. For new class in Mobile Application and Technology, Fling Standard [7] is to be used alongside Pressman. Problems arise when using Pressman Standard. In there around 8 to 13 UML form should be made. No indexing to protect consistence across UML diagrams. Consistence of design across UML diagrams, measured on consistence of indexing. For example, a simple use case should relate to one or several view class, all using same index. Long duration of design, typically around 3 months. Total student research duration is 4 months. Robustness of design, measured on the existence, not numbers, of benefit and consequences per stakeholders. 2011 ACEEE DOI: 02.ACT.2011.03.74

Short Paper Proc. of Int. Conf. on Advances in Computing, Control, and Telecommunication Technologies 2011 Interface Design describes the structure and manners the system interacting with its stakeholders, normally denoted like Component Design or User Interface Design. Architectural Design describes the structure of whole system, the notation is not standardized. Data / Class Design describe how the resources are retained in the system, normally denoted using Class Diagram or Entity Relationship Diagram. 2.2. Receive payment per goods sold. 2.3. Get info for popular goods and designs 3. Customer able to 3.1. Buy the goods created from a design 3.2. Request new design Each diagram created below shall not be a complete diagram. B. System Diagram The system diagram as in Figure 2. Creator should focus on one activity on one stakeholder at a time. For every activities, make sure that the Info View, Response View (if applicable), and Notification View provided. The ideal stakeholder is when he / she / it get something of value from the system, so he / she / it shall give something to the system. The normal stakeholder is when system gives something of value to him / her / it without another in return. The developer can quickly know if any stakeholder is milked, that is to give something without any in return. This situation must be avoided. If we dissect the diagram, one dotted square equal to one use case diagram. The diagram itself is a data flow diagram, assuming the system using data centred or centralized architecture.

Figure 1. Pressman Standard [6]

D. Proposed Solution We proposed several simple design notations in class as precursor to UML, mainly to make sure the design address the problem founds. We use the word precursor, not substitute, to stress that the design can easily converted to UML Models. System Diagram aim to show the prudence of indexing and robustness of design to student, as precursor to Scenario, Flow, and Architectural Design. Modified Class Responsibility Collaborator Diagram aim to show the robustness of design, using information from system diagram to student, as precursor of Interface and Behavioural Design, Modified Class Diagram to show the development of component using Model View Controller Architecture to student, as precursor of Class and Component Diagram. Relationship Diagram is kept the same as in [6]. The modification is not in notation, but in paradigm of design. This shall be the Data Class Diagram. The design is mean to be created by Software Engineer level. Knowledge on implementation platform is needed. E. Research Aim The research aim to introduce the simplified diagram to research student, and to measure the effect of system implementation and difference in consistence of indexing, robustness, and overall development time. Sample taken from Research-Lab! Student from 2008 to 2010, ranging from research and internship students. II. METHODS A. Case Used as Illustrations For purpose of illustration, we used simplified Fashion Designer Mobile System case. This system has three stakeholders, Designer, Producer, and Customer. 1. As a requirement, Designer able to: 1.1. put his / her design on the system 1.2. receive royalties if the design sold 1.3. get consumer design demand 2. Producer able to: 2.1. Realize the design and put his / her owns selling price. 2011 ACEEE DOI: 02.ACT.2011.03.74 124

Figure 2. System Diagram for Requirement 1.1. Designer able to put his / her design on the system

C. Modified Class Responsibility Collaborator (CRC) / Storyboard Diagram The Modified CRC Diagram is as in Figure 3, the CRC modified to double up as a storyboard, to give programmer general view how the system interact with the stakeholder. The diagram is made only if the System Diagram already made. One CRC Diagram equal one view and equal one scenario in System Diagram. The diagram itself is an Interface Diagram including logical explanations ranging from behaviour and navigations.

Figure 3. CRC 1.1.B. Input Design

Short Paper Proc. of Int. Conf. on Advances in Computing, Control, and Telecommunication Technologies 2011 D. Modified Class Diagram The modified class diagram is as in Figure 4. This Class Diagram is an ordinary Class Diagram, but made in MVC manner (16). This diagram can be easily converted to Class Diagram. This diagram is made using the data on CRC diagram, all goes to View section. The Controller section is filled using each of the technology unit needed. The Model section filled with each of the entity needed. Knowledge in technology platform used is essentials, otherwise the Controller section is impossible to fill. The Model section should contain any Object that can be used, both physical and conceptual object. All calculation is quantified into 0 or 1, separating satisfactory or not.
TABLE I. RESEARCH
SAMPLES

III. RESULT Implementation of aforementioned system yields result as in Table 2. The datasheet is not given due to size.
TABLE II. MEASUREMENT
RESULT

Figure 4. Class 1.1. Input Design

E. Entity Relationship Diagram The Entity Relationship Diagram is as in Figure 5. The diagram should made in strict entity relationship model; All entity is taken from model section in class diagram. It never have key from other entity. It never in direct relation with other entity. Sometimes it is safe to combine several entities into one; technically called generalization, if an only if the object itself is generally the same, e.g., designer, customer, and producer to be combined as user, name entityUser. All relation should be created from active relation between entities. Therefore student condoned to name their relationship with member entities and what relation they are in, e.g., relationDesignerCreateDesign. Relation table made to contain the entire foreign id from all entities related, and all the attributes born from that relation.

IV. DISCUSSIONS Pre system implementation system low scores caused by several facts. The use of indexing system when designing is yet to be common for Binus student. Furthermore, the use of indexing system is not normally condoned. Consistence of design is not condoned in practice in Binus. It only regarded for interface design. Normal design duration in Binus is 3 months. Much time lost on waiting approval time. At that time, research development aims mainly on technology and control unit, not system. Mediocre correlation coefficient on system implementation caused by several facts: The aforementioned system is still in testing phases, many aspects still in research, such methods to define system diagram. All the calculation assumed that all requirement shall not change upon delivery, which not always the true case. Robustness is the hardest issue to tackle, the system clearly show that it still ineffective. Robustness of design itself tied with proficiency with the platform used, which is not the case for students. Decrease in design duration mainly stem from shift (or rather, shift back) from flow based logic (such as when using activity diagram) and object based logic (when using use case and class diagram) to entity communication based logic, shifting the paradigm from tools to system development. The hardest part is to teach student that data and system class diagram is actually a separate diagram. In Binus, student often create class diagram as how entities communicate and what that entities do, which in reality, system class diagram should be a representation of system development architecture. Furthermore, for MVC style developer condoned to separate entity methods to view classes, while retaining basic function on controller classes, rather than to keep it in model. On the other hand, to change student way to create data design is hard; they not normally taught to regard data as collection of real life entities and

Figure 5. ERD 1.1. Designer Create Design

F. Evaluation Method System evaluated using comparison method. Data taken from Research-Lab! student from 2008 to 2010, which as in Table 1. Unevenness of number of samples is unavoidable due to Lab natural development. The technique is implemented in 2010, starting from idea competition. All research before that done using full Pressman Standard. The evaluation measured using 5 parameters. Evaluation made from derived UML design. 1. The effect of system implementation across 4 other parameters, calculated using (22). 2. Existence of indexing system across designs, exist better. 3. Consistence of indexing system across design, or consistence of design across designs, if the indexing system not exists. Consistence is better. 4. Duration of design, shorter better. 5. Robustness of design, measured in existence of benefit and consequences upon stakeholders, and completeness of stakeholders and features. 125 2011 ACEEE DOI: 02.ACT.2011.03.74

Short Paper Proc. of Int. Conf. on Advances in Computing, Control, and Telecommunication Technologies 2011 their relation upon each others, rather to regard them as collection of data and transactions made between them. That yields several data design problem, such as mixing design between normal 3 or 4, and fail to distinguish between entities and transactions. Future research should be made to attempt those issues. Robustness of design should be the top priorities. Several possible attempts can be made to tackle those problems. Student should be taught to think by whole system first when designing a solution, rather to address a stakeholder and their requirement first. His should be taught early; we proposed at most on 5th to 6th semester. Binus should have a convention or standard for student solution development, such as what mandatory components like encryption, update, and logging controller. Longer research period should be made to give student enough time to observe their chosen platform. Further research needed to find better standard on small project solution design. CONCLUSIONS The proposed solution proved to partly alleviate problems when using Pressman Standard for small solution development. Change on how software engineering taught is imminent in Binus, aim to shift student paradigm from tools to system development. Further research needed to find alternatives on design methods for small project. ACKNOWLEDGMENT Renan Prasta Jenie would say thanks to every member of Research-Lab! for enabling this research. Renan Prasta Jenie would say thanks to Gintoro F.X., Eddy Santosa Jaya, and the Information technology Directorate to provide place and facilities for this research. REFERENCES
[1] Information Technology Directorate Bina Nusantara Foundation. Research-Lab! [Online] 2011. [Cited: 22 August 2011.] http://ict.binus.edu/metamorph/researchlab.asp. [2] Long, Lyle N. The Critical Need for Software Engineering Education. Philadelphia University Jordan. [Online] 2008. [Cited: 22 August 2011.] http://www.philadelphia.edu.jo/courses/se/ 0801long.pdf. [3] Bina Nusantara Foundation. Vision and Mission. New BinusMaya. [Online] 2010. [Cited: 27 November 2010.] http:// www.binus.ac.id/About.Us/Vision.and.Mission/English. [4] von Konsky, Brian R., Hay, David and Hart, Bob. Skill Set Visualisation for Software Engineering Job Positions at Varying Levels of Autonomy and Responsibility. Curtin Department of Computing. [Online] 2008. [Cited: 22 August 2011.] http:// www.computing.edu.au/~bvk/papers/ASWEC2008-Skills.pdf. [5] Poslad, S. Ubiquitous Computing, Smart Devices, Environments, and Interactions. West Sussex : John Wiley & Sons Ltd, 2009. 978-0-470-03560-3. [6] Pressman, R. S. Software Engineering: A Practitioners Approach, Seventh Edition. New York : McGraw-Hill, 2010. 9780-07-337597-7. [7] Fling, B. Mobile Design and Development: Practical Concepts and Techniques for Creating Mobile Sites and Web Apps. Sebastopol : OReilly Media, Inc., 2009. 978-0-596-15544-5. [8] Laporte, Claude Y., Alexandre, Simon and OConnor, Rory V. A Software Engineering Lifecycle Standard for Very Small Enterprises. SpringerLink. [Online] 2008. [Cited: 22 August 2011.] http://www.springerlink.com/content/g04651327tq9v618/. [9] Pino, Francisco J., Garca, Felix and Piattin, Mario. Software process improvement in small and medium software enterprises: a systematic review. SpringerLink. [Online] 2008. [Cited: 22 August 2011.] http://www.springerlink.com/index/8261862588u07457.pdf. [10] Silingas, Darius and Butleris, Rimantas. UML-Intensive Framework for Modeling Software Requirements. No Magic Training and Information Portal. [Online] 2008. [Cited: 22 August 2011.] http://training.nomagic.com/attachments/288_umlintensive_framework_for_modeling_software_requirements.pdf. [11] Suri, P. K. and Singh, Gurdev. Software design simulation for quick and qualitative application development. IJCSNS International Journal of Computer Science and Network Security. [Online] 2009. [Cited: 22 August 2011.] http://paper.ijcsns.org/ 07_book/200908/20090812.pdf. [12] Bell, Jonathan, Sheth, Swapneel and Kaiser, Gail. Secret Ninja Testing with HALO Software Engineering. Computer Science Columbia University. [Online] 2011. [Cited: 22 August 2011.] http:/ / ww w1 . cs.colu m bia. edu /~ swapn eel/papers/ halo-testingSSE2011.pdf. [13] Tiwari, Vinay. Software Engineering Issues in Development Models of Open Source Software. Internasional Journal of Computer Science and Technology. [Online] 2011. [Cited: 22 August 2011.] http://www.ijcst.com/vol22/1/vinay.pdf. [14] Kaufmann, Markus, et al. Guide for Using Open Source Software (OSS) in Regulated Industries based on GAMP. vialis. [Online] Computerized Pharmaceutical Applications, 2010. [Cited: 22 August 2011.] http://www.vialis.at/fileadmin/files/imgs/pdf/ Newsletter/q3-10/OpenSourceSoftware.pdf. [15] Narasimhan, V. Lakshmi, Parthasarathy, P. T. and Das, M. Evaluation of a Suite of Metrics for Component Based Software Engineering (CBSE). The Journal of Issues in Informing Science and Information Technology. [Online] 2009. [Cited: 22 August 2011.] http://iisit.org/Vol6/IISITv6p731-740Narasimhan652.pdf. [16] Microsoft. Model-View-Controller. MSDN. [Online] Microsoft, 2011. [Cited: 25 August 2011.] http:// msdn.microsoft.com/en-us/library/ff649643.aspx. [17] Zeidler, Christian, Kittl, Christian and Petrovic, Otto. An integrated product development process for mobile software. Inderscience Publishers. [Online] 2008. [Cited: 22 August 2011.] http://inderscience.metapress.com/index/6k50u501456ttk1q.pdf. [18] Dupuy-Chessa, S., Godet-Bar, G. and Prez-Medina, J.-L. A Software Engineering Method for the Design of Mixed Reality Systems. SpringerLink. [Online] 2010. [Cited: 22 August 2011.] http://www.springerlink.com/index/J604TG736346H36W.pdf. [19] Appcelerator Inc. Appcelerator. Appcelerator. [Online] Appcelerator Inc., 2011. [Cited: 22 August 2011.] http:// www.appcelerator.com/. [20] gitorious.com. Gitorious. Gitorious. [Online] gitorious.com, 2011. [Cited: 22 August 2011.] http://gitorious.org/. [21] Koschmider, Agnes, Song, Minseok and Reijers, Hajo A. Social Software for Modeling Business Processes. SpringerLink. [Online] 2009. [Cited: 22 August 2011.] http://www.springerlink.com/ content/j72476tv12292v66/. [22] Weisstein, Eric W. Correlation Coefficient. MathWorldA Wolfram Web Resource. [Online] Wolfram Research, Inc., 2011. [Cited: 8 September 2011.] http://mathworld.wolfram.com/ CorrelationCoefficient.html.

2011 ACEEE DOI: 02.ACT.2011.03.74

126