bilgiz.org

Sdd template

  • 1.0. Giriş 1.1. Amaç
  • 1.3. Sözlük 1.4. Referanslar
  • 4.0 Sistemin nesne yönelimli tasarımı
  • 5.2 Database Tasarımı ERD Tasarımı kullanılabilir. Her entity açıklanabilir, önemli parçalar detalandırılır. 5.0 Use Case Realizations
  • 6.0 User Interface Design
  • Test Case Proje Yönetim Tasarım



  • Tarih27.12.2017
    Büyüklüğü18.07 Kb.
    TipiYazı

    Indir 18.07 Kb.

    Software Design Description
    Version




    Örn: Mağazacılık Yazılım Tasarım Dökümanı


    Table of Contents




    1. List of Figures


    1. 1.0. Giriş

      1. 1.1. Amaç


    < SRS Dökümanına benzer bir şekilde proje amacı tanımlanıyor >
      1. 1.2. Kapsam


    < Kullanılan tasarım methodları, sistemin genel yapısı ve ürün hakkındaki genel bilgiler. Harici sistemlerin tanımı ve ilişkiler. >
      1. 1.3. Sözlük


    < Kullanılan terimler ve anlamları, kısaltmalar >
      1. 1.4. Referanslar


    < Kullanılan diğer dökümanlara referanslar (SRS Gibi)>
      1. 1.5. Döküman Taslağı


    < Dökümanın kullanımının açıklanması. >

    1. 2.0. Deployment Diagram

    web browser

    talep ekrani

    personel muduru onay ekranı

    seyahat mudurlugu onay ekranı

    A
    cente ekranı

    The deployment diagram provides a physical look at the system with each processor and device indicated. This provides a background for the rest of the document as no software component can straddle two physical locations. Each physical location will have its own software unit and units in different physical locations will collaborate to provide the services that logically seem to be straddling the units. >

    1. 3.0. Mimari Tasarım







    < A software system is a set of communicating entities that collaborate to perform a task. The Architectural Design shows these entities, their relationships and the relationship to the actors in the system. This top level is a diagram where each entity has a name, a (proto-) type, an abstract specification and an interface design. The abstract specification is a description of its purpose, its functionality, its attributes (including dependency on other entities) and the constraints under which it must operate. It also describes resources, that is, any elements used by the entity which are external to the design such as physical devices (e.g., printers), software services (e.g., math libraries) and processing resources (e.g., buffers). The interface design is the list of the services that it provides to clients. These services are methods (procedures and functions), each carefully documented using a pre-condition/post-condition formalism.
    Each entity in turn may provide its services by having an internal architectural design with its own set of subordinate entities. These entities may be called sub-systems, components, modules or classes. The decomposition of a higher-level entity into subordinate entities must be explicit. The algorithm that shows how each method of the larger entity is performed by these components must be explicit. Any data stored in an entity must be explicitly described (see Data Structure Design below).
    Note that while the abstract specification (architecture) and the interface (detailed) design are usually developed separately in an iterative approach, they are combined for documentation. >

    4.0 Sistemin nesne yönelimli tasarımı


    NOT: Nesneye yönelik yaklaşımla system tasarlanmıyorsa bu durumda yapısal (structured) tasarım kullanılmalıdır.

    Çalışan

    Hem personel hem de müdür olabilir. Müdür olan çalışanın yetkisi personelden faklı olamlıdır.


    Seyehat müdürlüğü

    Iki adet iptal fonksiyonu vardır, birisi acente diğeri perrsonelden gelen iptal talepleri içindir.

    İptal talebi acenteden geliyorsa hem personel hemde müdür bilgilendirilir.

    Senaryolar için

    UML Sequence Diyagramı burada bulunur

    Flow Chart ve transition diagram gerekiyorsa konulur



        1. 5.0. Data Design


    5.1. Data Structure Design

    Örnek olarak Acenteden gelen farklı billet alternatifleri 3 boyutlu bir dizide durmalıdır. 1. boyut tarih bilgisi, 2. boyut şirket bilgisi veri olarak da fiyat bilgisi gelecektir.

    Karar ağacı var ağaç kodlanacak

    Acenteye bilgiler sırayla gitmesi için bir queue’ya konulacak.
    < If not already covered above, design in detail and specify the data structures to be used in the implementation. If these include databases, define the table structure of all databases including full field descriptions and all relations. Graphical languages are appropriate. Note that a database is an object and may have been fully described in the previous section. If the material is covered under Architectural Design, this section is omitted. >

    5.2 Database Tasarımı


    ERD Tasarımı kullanılabilir.
    Her entity açıklanabilir, önemli parçalar detalandırılır.

    1. 5.0 Use Case Realizations







    1. < For each use case in the Requirements Specification there must be a use case realization here. That is, there must be a sequence of events using the design objects that will perform all of the operations promised in the SRS. It is possible that there will be several use case realizations here to show all the alternative and exception paths required. The relationship between use case specifications (full descriptions in the SRS) and use case realizations must be bi-directional (referenced from SRS to here and from here to SRS) and explicit. Each use case realization must also be cross-referenced to the use case test in the test design. This relationship between use case specifications and use case test must be bi-directional and explicit. >6.0. Real-Time Design


    < If relevant, tell how your design that will ensure that the real-time timing constraints will be met. If not relevant, omit this section. >
    1. 6.0 User Interface Design




    1. < Refer to User Interface material in the SRS and supplement with any design considerations not mentioned there. You should discuss the expected effectiveness of your design. >

    Login Screen



    • Userid

    • Password

    • Ok button

    • Cancel Button

    Failure Message


    Personel Ekranı

    • Talpte bulunuyor

      • Tarih(gidiş dönüş) (TB2)

      • Talep No(TB Flex (30) )

      • Gidilecek yer(TB)

      • Sebep(TB)

      • Emir no(TB)

    Müdür Ekranı

    ….
    Seyahat Müdürü Ekranı

    …..



    1. 7.0 Help System Design


    < Describe the structure of the help system and how it is to be accessed. Will it be context sensitive? Will there be a system reference capability? >

    Test Case



    Proje Yönetim Tasarım




    1. Index



    < generate here >








        Ana sayfa


    Sdd template

    Indir 18.07 Kb.