Week-11

-

 

Hello blog (mood-status: feeling Good), writing this blog after thanksgiving dinner and eating well like pretty good with a plate of food alongside hanging the family. But anyway, on writing about this week-11. To be truthful here, I writing this because I am falling behind on blogs when there is nothing to talk about, besides kept being busy with other courses like HWs and projects, etc. (You get the point. Well, if you are a student) 

I decided to go on the Syllabus to look at the course topics.

I found the subject of Modeling along with Unified Modeling Language (UML) & C4 Model.


Unified Modeling Language

Large Companies' applications that execute core business applications and keep a company going can more than some code modules. It can structure in a way that enables:

  • scalability
  • security 
  • robust execution under stressful conditions. 


Their structure is that maintenance programmers can find and fix a bug that shows up after moving on to other projects. These programs can design to work perfectly in many areas, and business functionality is not the only one. A well-designed architecture benefits any program, and not only the largest ones as singled out. It mentioned large applications first because the structure deals with complexity, so the benefits of the network compound as the application size grows large. 

Another use of a structure that enables code reuse was design time. Ultimately, companies build up models of parts, each unit representing an implementation stored in code modules. At coding time, the developer can as promptly import the code module into the application. When another application needs the same functionality, the designer can quickly import its module from the library.


The C4 model


The C4 model made by Simon Brown designates on UML and the 4+1 architectural view model. It breaks down software into smaller units for modeling. Like the quick methodology, the C4 model requires fast, efficient sharing and constant updates of software architecture in software development.


The C4 model (shown as a map). The Maps can build on a different scale. By changing scales, like for example; The town map with streets and buildings. Having the C4 model changes the level of a diagram to describe software architecture. Using the abstraction-first approach, C4 conducts modeling top-down from system context to lower levels.


  • Person (Element) - users or roles of a software system
  • Software system (topmost level in abstractions) - the value of existing systems or systems under development and the interaction between those systems
  • Container (Element) - the internals of software systems, usually applications or solutions for data storage. A different concept to containers in Docker. It mainly refers to software that is single deployed.
  • Component (Abstraction element) - The containers of modules or a set of interfaces grouped as a functional unit.
  • Relations - dependencies or data flow between abstraction elements.

Comments

  1. Andrew LamNovember 27, 2021 at 10:20 PM

    This information supports me in learning and understanding the topic for the CS course. The material can students expect to apply what was learned in their future practice by small subject containing many types of information.
    _______________________________________________________________________________________________
    URL links-
    _______________________________________________________________________________________________
    The link has Understanding of The C4 model
    ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓
    https://engineering.linecorp.com/en/blog/diagramming-software-architecture-using-c4-model-and-c4-plantuml/#DiagrammingsoftwarearchitectureusingC4modelandC4PlantUML_ko-C4%EB%AA%A8%EB%8D%B8
    _______________________________________________________________________________________________

    The link has Understanding of What is UML
    ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓
    https://www.uml.org/what-is-uml.htm

    ReplyDelete

Post a Comment

Popular posts from this blog

week-3

-
Hello, I am doing some class activities and looking over some questions ahead to save time for a thing or two. I came across the word "Behavioral Patterns" in class Act. 4 (Model 8); I got curious and looked it up. I found two articles that helped me understand the purposes, Problems with solutions, Real-World Analogy, Structure, Pseudo-code, Applicability, How to Implement, Pros and Cons, Relations with Other Patterns. The Behavioral Patterns are concerned with providing solutions. It is about object interaction - how they communicate, how some are dependent on others, how to separate them to be both dependent and independent, and give both flexibility and testing capabilities—also, the assignment of responsibilities between objects. The Behavioral Patterns cover many small parts to form the full extend of patterns. Like Interpreter, Template Method/Pattern, Chain of Responsibility, Command, Iterator, Mediator, Memento, Observer, State, Strategy, and Visitor. Interpreter The
Read more

weekly blog (week one)

-
Hello, Everyone. How are you guys doing? This past week, I read some articles or news related to CS (Computer Science). I finally picked a topic that caught my attention; engineers create 3D-printed objects that sense how users interact. My reason for why and seeing how choosing this article is because it looks cool and relatable for Gamers to use any controller made of small rubber pieces.    Short Summary : The researchers found a way to combine sensing capabilities into 3D printable structures made of constant cells, enabling designers to prototype interactive input devices quickly. Even, Formed a new method to 3D print mechanisms that detect how force applies to an object. Or The structures are made from a single piece of material so that they can be rapidly prototypes. Also, A designer could use this method to 3D print "interactive input devices," as a joystick or a controller. For accomplishing the goal, the researchers blended electrodes into structures made from metam
Read more

week-9

-
Hello, week-9. I want to post a blog to quickly review the API topic to learn more about  REST  calls. I got confused; I researched about it. It has the Understanding And Using REST APIs.   What is a REST API   API (Application Programming Interface) - A set of rules allows programs to support any other. The developer creates the API on the server and enables the client to speak to it.  The REST (Representational State Transfer) determines how the API. It is a set of rules that developers follow when they create their API. One of the rules states that one should get data (called a resource) when linking to a specific URL. Each URL made a request, while the data sent back to is called a response. The Anatomy Of A Request # It’s important to know that a request with four points: The endpoint The method The headers The data (or body)   The endpoint  - URL that requests for (root-endpoint/?). The root-endpoint is the starting point of the API that is ordering. The path determines the resou
Read more