Skip to main content

Software Design and Architecture

 

 
         Architecture is the stuff that is really, really hard to change later.
 

  • Design (The Small Stuff): Choosing whether to use a for loop or a while loop. If you mess this up, you can fix it in 10 seconds. Design is the noun (the plan) and the verb (the thinking process) of arranging your components. 

  • Architecture (The Big Stuff): Deciding to use a specific database or deciding how your app talks to the internet. If you mess this up and realize it a year later, you might have to delete everything and start over.

     

     1.  SRS (Software Requirement Specification)
     
    The SRS is the contract. It describes the features. If it is written in the SRS, the software must do it. If it is not in the SRS, the software will not do it. 

      2. NFR (Non-Functional Requirements)

    NFRs do not describe what the software does (features). They describe how well it does it. We call these the "ilities": Reliability, Scalability, Usability. 

     

     Training Usability (The "Grandma Test")
    "How easy is it to learn?"
     This measures how long it takes a brand-new user to figure out how to do their job without asking for help.
     
    2. Operational Usability (The "Stress Test")
    "How does it behave under pressure?"
    Training usability is about the first time you use it. Operational usability is about the thousandth time you use it. It focuses on efficiency and speed when the user is an expert.
     
    3. Thresholds (The "Pass/Fail" Bar)
    "Where do we draw the line?"
    This is the most critical concept for an Engineer. You must define a specific number (a threshold) where "Good" turns into "Bad." If you don't set a threshold, you can't fail the software.
     
    Summary of Module 5
    1. Be an Engineer, not a Coder: Be Systematic, Disciplined, and Quantifiable.
    2. Respect the Order: Don't code before you design. Don't design before you know the requirements.
    3. Design in Layers: Start with the data (Storage), then the structure (Architecture), then the look (Interface), and finally the logic (Component).
     
     
     
     
     
     
     

     

     

     

     

 
Labels:

Comments

Post a Comment

Popular posts from this blog

Java Servlets

  According to me its just a translator, who manages the HTTP requests and handle them to the appropriate function of the API. So then, API turns out to be a term or set of those functions which are kept public. Now let us see in little bit of detail what servlets are: For that we need to see few terms: Static Web Pages: Static web pages are the pages, which are already built, and whose content and design always remain the same.  For Example: About us page of some website. Contact info page of some website Dynamic Web Pages: Dynamic pages are not already defined. They are dependent on search queries. For Example: If we search top 5 books, and click on search button, result would be different. If we search top 5 countries and enter search, result would be different.  So, the search result for every search is different. Working: Now if we have to search static page let's say the first page of any website (which is same for every use in every country) then the process is sim...
Post a Comment
Read more

What is an API? A Simple Explanation for Programming Beginners

API What is an interface? Interface is a control system, through which we can use something. For Example: The interface of car includes: Steering Wheel Brakes Gear Acceleration pedal Mirrors Interface is concerned with the fact that how to use something, rather than how it works. The Easiest Analogy for an API : The Restaurant Imagine you're at a  restaurant . You are the user. You want food (data or a service). You can't just walk into the kitchen and start cooking. That would be  chaotic  and unsafe! Instead, you interact with the  waiter . You look at a  menu  (the  API  documentation) and give your order to the waiter. The waiter takes your request to the kitchen. The kitchen prepares your food. The waiter then brings the response (your delicious meal) back to you. The  waiter  is the contract, the messenger, the interface in our case the  API . They provide a secure and simple way for you to get what you need from the kitchen ...
Post a Comment
Read more

Why do I need to create Java Classes? Why don't just use database for searching?

The Bridge Between Data and Display A Conceptual Guide to Java, Databases, and the "Why" behind the Code. 1. The Core Problem When building a web application, you have data sitting in a Database (SQL Server) and a user waiting at a Browser . The challenge is moving that data efficiently and safely. Beginners often ask: "Why do I need to create Java Classes ( Student.java ) and copy data into Lists? Why can't I just print the database results directly to the screen?" To answer this, we must understand how the database actually talks to Java. 2. The Anatomy of a Connection The ResultSet is NOT Data — It is a "Live Wire" A common misconception is that when you run a query, the data is instantly sent to your Java program. It is not. The ResultSet is a Cursor (Pointer) . It points to a row on the database hard drive. The Connection is a Pipe . The Streaming Analogy: Think of a ResultSet like a Phone Call . When you say rs.next() , you are asking the da...
Post a Comment
Read more