|44 - Title||Methodology of Software Development, Sesam - Turkuaz|
|Authors||Osman Ataker, Sesam Yazılım Hizmetleri |
|Contact person||F.Tayyar Öncü, email@example.com , 0212 3360316 / 4507|
|Main Fields||2. E-ticaret, E-is, yeni-ekonomi
14. Yeni internet Teknolojileri ve Teknik konular
|Other Main Fields|
|Abstract + Keywords|
Sesam utilizes object oriented analysis, design and development methods troughout the whole lifecycle of software projects. The hybrid in-house methodology is a combination of best parts of the modern techniques in use today and is supported by an in-house application development framework called Turkuaz that holds the whole process together. Turkuaz serves as the knowledge base shared by the whole project team, enforces the technical architecture principles and generates interfaces and code for the development team. As such it is an important asset of Sesam and is recognized and financially supported by Tübitak (The Scientific and Technical Research Council of Turkey) as a research and development project.
Regardless of the functionality they offer, all applications developed using Turkuaz consist of four layers of objects handling the different responsibilities. This architecture is an enhancement of SmallTalk MVC and achieves a high level of encapsulation and separation of the implementation from the interface. Four layers separate the user interfaces, use cases (scenarios), business logic and data neatly from each other and they communicate with each other via well defined protocols. This architecture not only raises the software quality to a new level but also makes it possible for large teams consisting of different roles to cooperate in the most productive way.
Interface generators of Turkuaz let the designers to create their solutions without the involvement of any developer. Given the specifications of the controllers they will use, designers use the in-house built XML to construct their interfaces and then use the generators to produce the server and client components automatically. This way they can design one interface and produce several component combinations without any developer intervention.
Code generators read the knowledge base created by the project team to automatically generate the source code of the application. The knowledge base acts as the application metadata (dictionary) and knows about the object architecture in every layer. All the property and method details of each and every class in the system as well as their relationships are kept in the metadata with the necessary documentation. Team members access this base with a web-enabled application which allows for location independent and continuous access to the project resources. As a matter of fact, even the application managing Turkuaz is built and generated by Turkuaz itself which shows the versatility and power of the environment.
|CyberChair||Author: Richard van de Stadt ( Borbala Online Conference Services )||Development supported by TRESE||Copyright © by University of Twente|