slide1 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Architecture Review PowerPoint Presentation
Download Presentation
Architecture Review

Loading in 2 Seconds...

play fullscreen
1 / 23

Architecture Review - PowerPoint PPT Presentation


  • 135 Views
  • Updated on

Architecture Review. Logical View: Layer Overview. Exhibits layer cohesion. Logical View: Presentation Layer. Logical View: Business Layer. Logical View: Data Access Layer. Process View. Development View. Physical View. TESTING. Test Plans.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

Architecture Review


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
    Presentation Transcript
    1. Architecture Review

    2. Logical View: Layer Overview Exhibits layer cohesion

    3. Logical View: Presentation Layer

    4. Logical View: Business Layer

    5. Logical View: Data Access Layer

    6. Process View

    7. Development View

    8. Physical View

    9. TESTING

    10. Test Plans The following input is required to test an application block: • Functional specifications • Requirements • Performance objectives

    11. Test Plans Test Methods : • Regression Testing • Integration Testing • Black Box Testing ( Stress Testing ) • Unit Testing ( N – Unit )

    12. Test Plans • Regression Testing: • Test fixed bugs promptly. • Watch for side effects of fixes. • Write a regression test for each bug fixed. • If two or more tests are similar, determine which is less effective and get rid of it. • Identify tests that the program consistently passes and archive them. • Focus on functional issues, not those related to design. • Make changes (small and large) to data and find any resulting corruption.

    13. Test Plans • Integration Testing: • Def: A type of testing in which software and/or hardware components are combined and tested to confirm that they interact according to their requirements • Check Connections : • Pocket PC ---------- Web Server • Web Server -------- SQL Server • Pocket PC ---------- Speech Server • Speech Server ---------- Web Server

    14. Test Plans • Stress Testing: • Evaluate the application block's behavior when it is pushed beyond peak load conditions. • The goal of stress testing is to identify errors that occur only under high load conditions.

    15. N-Unit Testing • Unit-Testing Method For All .NET Languages • Assertions • Comparisons • Condition Tests

    16. Comparisons • Report Expected and Actual Values • Assert.AreEqual • Both arguments are of the same datatype • Ex.(Assert.AreEqual Int Expected, Int Actual) in Transfer Balance • Assert.AreSame • Same Objects are referenced by both arguments

    17. Condition Tests • Assert.IsTrue(Bool Condition) • Assert.IsFalse(Bool Condition) • Ex. Assert.IsTrue(hash.MeetsPassword(“goodpass”), “Good password failed check”); • Assert.IsFalse(hash.MeetsPassword(“badpass”), “Bad password passed check”);

    18. COCOMO • Total lines of code = 41.8 function points * 53 lines per function point • Total lines of code = 2215.4 • KLOC therefore equals 2.22 • E = bKLOCc • The basic COCOMO parameters for a semidetached project are b = 3.0 and c = 1.12 • E = 3.0 (2.22)1.12 • E = 7.328 staff months

    19. COCOMO • Student months = 4 * 7.328 = 29.02 • 29.02 student months / 7 students = 4.2 months

    20. QFD Analysis

    21. ICED-T

    22. ICED-T

    23. THE END QUESTIONS?