Let me get started. Okay. So okay, so today I'll be explaining documentation part of the documentation and we'll start because we have three days right whenever they felt their credit 21st 22nd will be no 21st I will be giving introduction to dB 22nd I'll be giving introduction will load and so, we have three days and I will cover the waterfall methodology and sdlc so we have not done with a DLC. So these are all theoretical part today I will start the documentation part okay. So Everyone has this access to Google Drive. So I told everyone to whoever doesn't have, you know, they need to request right or send me an email address for that really gave you access to this.

So, here, let me know. Okay, it's a business required document. So as I told you, business record document Okay, so, the business a comment, so the documentation right. So, what are the business requirement document contains so business require document contains 10 to 20% of use cases, okay business modeling, risk analysis budget This is the information that business okay. Let me show you how does that look like okay. So that is actually theoretical definition of a business requirement.

We conducted a lot of information for the, you know, for developers for the testers for project managers, Scrum Master managers, for everyone it contains a lot of information, but we will not be using you know all of that Only the information which is required by the testers will be using that Because see, that is very huge like you don't understand everything nobody understand even I don't understand every business requirement. Document Why? Because it's not meant to everything it was meant to. To know all the team members, okay, there are so many people who I can read don't have cards, testers. So it's for them. So it has a lot of information in it.

We will be only working on what is required. Okay, let's see. Let's take in simple business conditions, the most simplest business comment, no, but they should not be in this. Okay. This is just an example to show you. It contains information.

Okay. And so the company logo and what you're trying to do here, okay, the table of contents, okay. There's requirement analysis and design. Okay. And then it has some information Okay, who is the region region and the name And then here are the functional requirements. So in this case right functional requirement there is no information this is more for developer point of view, how does it should look like as a tester, I will see only first name, okay, so this is a field I need to test.

So this is the field which I need to test. Okay, so that's the show I'm showing you right now that it looks like I don't understand. Like, text like similar example. Like we have like this one and see how name read this field. So we have to make sure this field should not accept any numbers and all this stuff. So that's how it is.

Okay, first name, last name. So we also have this last name stuff offered. See, okay, this is mixed in with this one, first name, last name, address. So this is how it contains Okay, address and city. It has to be good and it has a state where everything No this no this kind of information. So this is this is like, this is coming from stone age's.

Okay, all this information will be there, and then have email, email and all this information and you need to test that. So this is how business requirement context but this is very small No, this doesn't happen real time this way. This is something which is really, you know, just like a joke. We don't have this for free, you're testing you're testing us, you're also making a very small you're testing a huge product in that image, some part of the 30 years or six. Okay, that would be so much big. Let's take in real time example.

Okay. So that was simple thing. Now real time so that everyone understands, okay, that's a joke, you know, a lot of information, whatever it is. Now, the hard part is like, you know, when you get a little document, okay, but this is our example I'm showing one Business Report document. Okay, so this is how it looks like. Okay, so you this is Business Report document, this is the real time.

Okay? So you have all the information here. So just show me things here, right executive summary, business definitions, current environment, project requirements, business requirements, and so on project ID and okay. And now we don't understand all this, nobody has to understand everything, only the exact thing you have done, you have to go through it but you have to read everything. Don't have to understand everything but you have to read everything because you don't know which part of your job right you need to understand. So here is the plugin I explained here, right?

With the product will create so whatever the underlying right that you need to understand from them, okay. And what know what the implementation for what is this and what it's working you know, is this smart Foundation, you do? Understand, okay, this is how it looks like when in our real time business requirement. See here this we don't have any screenshots Okay, there can be injured. I mean there is no English okay. So that's a functional requirement functional requirement document is like you know, okay, so in functional required document right.

It contains what it contains it contains no functionality of functional and features of an application. So as I told you read it kept this also contains the screenshot, screenshot of this page, click on all these pages on how does it look like this billing information might be in a somewhere place and this email might be here. Okay, all those things Consider the screenshots and the information to know what has happened when you click on Place Order. So, this is this should pop up, okay, is this this kind of information should be then the fit the functional requirement document. So let's see, let's take an example out of it looks like okay. So this is how you know, similar to business requirement, but this is more specific to functionality and features of an application.

Okay. So these might contain some screenshots, some information about that. Okay, requirement is like some company Getting uncomfortable, we usually change our DVR to seeing them say, okay, they might know us the same thing for their own purpose, that's fine. But normally it's a two different things. Okay, for because if some company right in small company want to see like they're like no, there are so many things they'll be using. Okay.

So this is for the content, the functionality and features of an application Brd contains like 10 to 20% use cases business modeling risk analysis and budget. Okay, so this is an example of a party. potion sticks. Okay? So that's how it looks like. Okay, you guys can look into it, okay?

Or no, you will even have access to Google Drive. Maybe I have to give access for you. No one gets paid more and people who are don't have that access to erect just send me an email for that. I'll either give you access or again you can navigate through your system specification systems require specification is like you know that is that is like it contains a complete architecture okay we present a complete architecture and also contains the about the software hardware information okay. So, that is SRS okay system required specification and then you have physical data modeling. So, this okay this document so, this is how it looks like okay this contains all the architecture information.

So, I mean this is model D everything will be there, start with the introduction right. So, these are Okay this is this will be a build of the company's name okay. So, what is doing and CEO What are they trying to do operating environment and all those information design and implementation constraints user documentation assumption or dependency So, there are some parking SRS system required specification okay what are the features before because and so there are so many things like you can go through it but in real time you need to understand this you are not where you know you go Don't go directly and write this documents by yourself but you need to understand So, what we are trying to do and what is the inverse document and how we are going to proceed. So, that's for that reason. Okay these documents you need to understand the architecture if you're trying to understand architecture, you need to know this okay.

So this is how it looks like. And then you have like high level design. So high level design high level design is like you know, you talk to like, you know, design document Okay, so it's a design document we normally connect you know call flows called flows are the flows which you have this like your flowchart which flowchart you want to know, let's say let's take an example like opposites like you're running in some third party tool, no job should you do so, you have a job scheduling tool you will be known or using? No, that kind of document is called either TDD Okay, and it's called the TDD technical design document. So this is this also similar to agility Okay, which is which contains all the all flow information on the know the flow charts, like are using some normal jobs and which job should run passion which is be more better understandable right.

Now, Mama, do you have any question? Okay, so this is again, let's see, technical design, Batman, Golding start from this. So you can have the technical information normally okay. So but this is not much appropriate to it, but you can take this as makes much more sense technical development okay there's a common theme here you see here the floor Do you see that diagram normally it contains these diagrams, okay, so that's why it's called us. Very good example. no information about the good.

Let's save this Okay, I'll be putting this into Google Drive okay. So CDs okay. So this kind of information about the high level diagrams, okay all the drawings you can choose either in diagrams, so normally flowcharts and call those all those are some screenshots. Okay, so that is technical design document STL social target medical everyone knows this what is a scam? So it's like source to target mapping. So the mapping document so how does the mapping document look like?

Okay, so Okay, so here it is it's a water the mapping of a conductor It is like source to target mapping document that is to say it contains all the information about the soul, okay about source information make sure database whose columns source table and all kind of information and also it contains information about the target, target column target, target table target database, you know how many database you are using, how many, okay how many columns and how many rows and how many tables All that information okay this is supposed to be there today STL photo target mapping document. So it has and it contains a transformation logic or transformation rules okay? what it's supposed to do okay how many okay when you're trying to do in a normal GIS are done that time target right on it conventionally normally that transformation is done in the target nada so but notice there are still things they know you will be doing like no resource you'll also be you know, putting transformation logic, okay, based on the complaints with all this information will be contained in this STL.

Okay, so this administration, let's say this is an assault. Okay? This is a confirmation logic and this isn't Information about what to do okay and this is a message okay this is a message format and whatever could refer additional recommendations like typical national governments, but this is not always like this you know there has to be short information target information then they need to proceed now you because you need to know the primary key no primary key natural key or candidate key all those information will be there any sto So, so target mapping and then you have two main party you have dish plan what is it discipline? So, CrashPlan is a high level document planning a high level document which contains all the information about the okay about the project. Give me a second Okay, so this plan contains all the information about these So it's a high level document prepared by the QA team, okay QA lead for more specific to the business a QA lead.

So you will be giving inputs like what do you need to be tested all this information about it? Okay? So, okay, you don't normally you don't prepare it, but if you're if you have to prepare it, then you have a very regular choice. Okay? So you have to prepare it, even as a tuition. But normally, it's the job of the community.

Okay, so what does it contain? So what are the test plan contains? Okay, that's the most important Okay, so we have this so it contains all information like you know, display and identifier, introduction, test items, features to be tested features not to be tested, approach, okay. And test deliverables, testing tasks, environment needs, all the information will be there any longer like topics and the same topics. Okay. Let's make this happen.

Better thing to show. So okay, so they'll be giving you homework on this test plan, okay? You need to know so this is a template of test plan okay this is there in the Google Drive or I can send you email okay? What do you need to do is you know, just change this information okay? This is Tagalog change it to product name as GMO okay and what we have done right GMO and we are trying to prepare a test plan for that okay. And GMO and you know, despawn is good as you can leave this alone and put the date what you're trying to do, okay.

This put wherever is a product name, put that you know, the GMO and then you can put as author name, okay. And all this information you can we can be like Yes, okay. Here what you can do is like what are trying to test? Okay, these three things you can fill it up like you know, you are trying to test online catalog page and online okay and the sales and the payment okay three things you can do whatever you want to add you can add it okay and items which are not to be tested okay you can also add items which are not to be tested okay you can put this information in this and then this is to be tested is not to be disturbed and this is to be does make sure you can remove items to be tested you can remove this and no this is not to be tested, you can remove this, okay?

And then do this. Okay, let's see this. This is functional testing. So what so make sure you guys are doing right, right? This is functional testing. So make sure you update in this.

What is this? This is conformance test. If you're not worried about this, you can leave it leave it just like that. Okay, functional testing make sure you edit the window functional testing module not in something as load testing. We are not worried about it. So just make it limited.

Performance testing is fine regression testing you can add some of these integration testing to and Okay, can stress testing, forget it. System testing if you want to add if you know what they have to provide, you can add unit testing, it's not our job to, you know, build up a user acceptance testing recipe no more so that you can okay fill you this information. It's simple Google Images just make sure which you're trying to do. Okay. And then just put your name role, okay. And then just upload that into the SharePoint which I have given you access.

Okay? That's not a whole lot. I'll be you know, giving you instructions make sure you follow the instructions and just do it what that as per the instructions okay. Okay, so this is test plan. Okay. So it contains all information like you know, risk, okay, what are the risk and what are no features?

Distance test approach all this information in conducting the test and this is how it looks like if you want to see how the test can look like this is how it looks like okay and this is the information that will be there. So, not only that in random Do you will be doing the same you know we are only editing it you will be removing all this okay you do not require any more putting this information and if we say they said okay no notice you trusted him we are not bothered about that then you will be removing that. So this is a very good example for no template for a Tesla. Okay, this is how you can use it. Just make sure you own a chain all this information project name GMO, like okay, you can add it that and then you can just know.

So that is okay. And one more we have this strategy roadmap. So what is it this strategy? Okay, so in the real game, right, the Microsoft's saying they cannot discipline their strategy or theme, but to me, you know, it's not a no I would not data to say No test management strategy different strategies who are there What is it a strategy tested see just plan is like how you're not planning. So, it contains all the information about planning things okay all your planning and what are you trying to do all those strategies continue like you know, statistical analysis like I know how you're trying to approach. So this is like planning, but if they are talking something how we are going to approach that that is strategy.

Okay. So what does it contain? So it contains test levels roles and responsibilities environment, the comments, testing tools, risk and mitigation, testing scheduled testing priorities, okay, all this requirement, traceability matters, all this content in the strategy document which doesn't have in the test plan. This is an example of a strategy. Okay. So last pass, fail criteria and all those conditions.

Okay, we've conducted any strategy document, rescan contingencies, okay? And then you have your list report responsibility matrix. So this is a test study. So technically test plan and test data the government integrated now I told you what's the difference right? So all the initial plan is like, you know, something you're planning, okay, you know, this contains all the information about the planning strategies like how are you want to approach so all the information about a project? Okay, information about a project can get going, you know, normally, you know, in a project, they might say, No, no, both of them so go with that.

You don't have to argue with them and say, No, no, the strategy is different. I don't know. You know, sometimes they call it test monitor strategy and strategy to test plan and both. They want to call it a safe that's fine. Don't worry about it because you just want reading and understanding nothing to do with anything that you need to if you want to design like you know que le will be helping you out and are mostly lead we'll be doing this and you will be okay. All right.

Next. So, next we have like a static test case. So everybody knows that test case is the high level document. Okay. So these all these things are like a high level document. But test plan and test strategies are high level document which is done by the lead.

Okay, QA lead test cases is a high level document which is done by a QA analyst or Minister Mr. Parrish. Anyone else is done by the QA least not yet. It's not who the Okay, so, test cases SPSS is like, you know, it's a high level document which contains which is you know, which is done by the QA. Okay QA team, QA analyst and QA district. Okay? What is it contains it contains like test case ID object you steps to perform expected result pass fail comment so normally we don't we didn't see these many right we just really could no actual and expected normally that's it but to be more theoretical point when you're trying to explain that you need to explain all this so you need to be very detail level detail oriented.

We're trying to say that you need to take all the information as much as possible so that you know more than anyone else, that's why they want to hire you right? Because you know more. Okay, so does needing me to tell all this information, what are the test case candidates make discuss ID objective steps to perform expected result pass fail, common. Okay, so the SK migration document for Migration document He's like, you know, it's like those other documents like, like, you can take it as an opportunity. Normally it's a project like there's another soul from IBM and they're trying to migrate that know that. I'm sorry DB source you have a DB two and we're trying to migrate data into Oracle.

Okay, so now you read my Okay, let's say data, data, data data and you're trying to make it in order. Okay, now let's say you need two separate documents Why do you need separate documents because see the query the SQL queries the The weather is the writing a sequel various different data and the different racket Okay, that's fine. But he has a very niche catch tone in this might be different okay. So and in the Oracle it is different. And then you need to know do a lot of data scrubbing data mapping, data, cleansing all those things. After doing all that, you know, you need to put into the Oracle database so all this information right All this information actually you're you're trying to, you know, migrate into an enter database, then you need to put into the migration.

So normally won't have to be a separate document, but it's just in case no. Normally if you have the documents then you will be having this migration. Okay, so this is all about documentation, any question in documentation? Okay, good. So we're actually going to check homework to the next let's go James Okay, so we have a density many lecture we will do mesh agency. So let's kick off Good luck.

Okay, good. Okay. There should be, you know, the more dignity open that you've got. I mean when Don't have to be you know exaggerating everything but enough unless trying to and I'm just trying to you know make you understand like you know if you haven't open defects you know you will be in a plus fight because they cannot do anything we do just that defect is close to me before the defect the closure, measure Yokohama defect so again they can't do anything so that's all you have to know move to the dimensions I showed you are the way you're doing the work okay. You're good We don't need much of technical skills. But if you're not good with constant then you know technical skills only help you okay so Got this is this is the one I was talking about.

Open that is important so that is that makes sense right? Does everyone agree that this is a perfect this one okay you're like a GDP you know? We're in taxes not a lot so why is as a customer I don't need this right? I don't want all this to know when I'm trying to navigate the webpage. This is an issue. Okay.

So of course you've been you know on your bank opening you discard these issues can be opened directly, but you need to first of course, best thing is you need to talk, you always need to talk. Okay? Without you don't do anything talking, right? If you do that, you know, you will get into trouble. So make sure you know, do it. What has been said, Okay, so you always need to be be proactive.

No, you need to talk to lead saying that, hey, you know, this is significant. You've not read and develop Scrum Master, national mastered and the product owner. So there's only people who do, you don't have to know. So it's no No, no, no. No leading my team. How can I proceed?

No, that's not the answer to someone as a developer. You know, you cannot say that there is no developer in your tester to retail should be a developer, okay? So that's what I mean when you need to be proactive. Not just you know, being taken granted of what I'm saying. You need to be so that you can get recognition so that you know Okay, we are doing some work now. Otherwise it will be hard.

Okay, so are you 17 Oh, getting serious maybe what it might be wrong. Six plus nine. Okay. Guiding check this one. Okay, this is good. This totaling procedure is incorrect and of course, he does a very good no point.

This is a very good point. I didn't know this. Right. So this is a very good thing to talk about. Whenever you get a chance you need to Talk about is Cuba how we are trying to do both? And yeah, I'm getting at in vt, but you know, what are we trying to tolerate is completely different.

Okay, so this is a very good defense. Okay, so this is something which I don't know, because I don't know in which browser it is happening. Okay, this for this, you need to be specific because for me, okay, if it isn't, this looks like more of a Google Chrome. This is browser because I'm aware that seeing that this can be Google Chrome. Okay, but I never got this issue. So I'm not sure like, you know how.

Okay, so it's in Firefox. Okay. So fear is all you need. Put that information. Okay? So for whatever you're trying to do, right, you need to put which browser.

Okay? And so that is so they'll have better knowledge than Okay. Is it an IE given Safari or is it in Firefox and Chrome for me? Right. Okay, so good good. Yeah, so this is exactly what activities so this thing, name and address doesn't follow the standards and interest requirements of okay mean this one okay?

Shipping okay so yeah I guess everyone has you know good eight screenshots that's good so they're doing well always okay to start with you can do this I mean see when you are experienced like an opera two three x EF experience the overlap between that and you might not even open defector No. Okay, so the starting that's a good start, okay you need to put a screenshot if you have more information, okay, what is know which browser it is which version it is, the more specific you are, the more the better things will be for you as well as for the others too. Okay. Okay, that incinerators been added more than or the stock okay? Make sense? So yeah, so all these right okay, so go right out like you know everyone almost everyone has to open that screenshot.

That's good. The screenshot is always important. Okay, so now let's go to his DLC for his DLCs are giving from three sides, maybe three to four slides to remaining we can continue tomorrow Okay sdlc software development lifecycle. Okay, and so you can go ahead and release emmc don't require this new CMM low probability maturity. But unless you want to read Okay, you can go ahead but it's not required at this point of time. Unless you want to read and really want to understand more, we can just have a glance at that because even if it is asked in the interview, you can you know, be smooth on that okay.

So sdlc sdlc is like software development lifecycle. And so, what are the sdlc contains sdlc contains phases so it contains messy information autism, LDL, LDL g soccer, local life check. It's an identity management process, it's an iterative and incremental process Only thing is I can either do an incremental process okay. So, it contains like phases various phases in the project. So, to be specific, it has 10 stages, okay, it has like 10 pages, you know, can you see that like initiation system concept planning requirements design development, integration testing implementation operation image in this project it has 10 phases but you know so I don't want to like you know, be more detail on it, let's stick to that. qualify this, okay.

I don't want to be more detail and you know, boring to you and the interviewer Of course, no, no wonder if you are if you know it, of course you can tell it but in there stick only to the five edges. No, six phases requirements, design implementation test. Installation maintenance satellite support okay. So what are the kinetics? six phases? Okay, this waterfall waterfall is a part of that.

So, these are waterfall A j in helical mer and then again your helical model and there's so many methodologies so these are methodologies okay these are all derived from sdlc software development lifecycle with the derived from the sdlc Okay. Let's see. So, when the requirements state already happened we know we you know gather all the requirements or be a business analyst to gather all the requirements and you know, put that requirement to replace and then you know, it gets approved for the manager the manager and all the stuff then it's get ready then decide for whatever it is like then you know, architecture job this is like more of architecture and says like no, no, we have to design this way. No that take that Architecture level and data modeling should be this you know, all those things that is design you're trying to design an implementation implementation is that more of it the local Java and saying that okay, we are trying to implement this this is the this table should be getting to this what is this website should be doing this and this is how to be sure that in implementation you're putting, we're putting one right once it's done, we wanted to move into testing them and then you test to that will be done the test and then once it then you test so you communicate with the middleware team or you know, or some load something and then you you know, put into the production.

So, that's the installation when you do the production in real time, okay, then and then you know, we will do a production support Okay, the maintenance so if you then bugs in production issues, there are some issues in the production, then you know, you have maybe, so this is like, you know, six stages, so can anyone can anyone tell me like which pays additional jobs, big interest Which phase the tester will start working on? So, this is like in six phases, but you know where the testing job stops okay. So, let me ask you this. So, in the district job starting up nothing. So, do you think that destiny will be I will have data and they will pay you for being idle okay. So if you have answered that right, so you have to answer this question.

So, if you think like, you know tested outside from design implementation test or from test So, do you think that all these phases of testing will be idle and they will pay you for being idle More, right? No and we pay you for being idle. Our job as a tester will start from the right from the requirements. Okay. Right from requirements for what will you do with the requirements so I know requirements requirements like this, although it's a job of a BA, a product owner, let's be you know, being a product owner job, okay? Although it's the job of a product owner to gather all the requirements and all the information and put it in one place, we will be no involved in that saying that okay.

So there will be our okay. So to start with, you know, you'll be just you know, moving into meetings here and there. But once we get experience, we will be there in all professions. And then you know, you have a meeting, meeting and developers know product owner, we have meeting the developers testers. Okay, our email architectures managers, okay, even if it's not, am I the Scrum Master? All in and say like, okay, This is the requirements for what we are going to do this is the production level you know come up with saying that okay this is the requirements we are going to implement it for how we any questions in that know any you know, you do, how do we want to proceed, but this is how the business shared that.

So, those kind of things now, I will senior desta, right, you will be looking at the requirements and the saying that, okay, so this is a requirement, so, okay, so it's more like a developer developer will say, Okay, so how can we proceed this? If there are issues of how we are going to proceed it? Do we have any statistical analysis? Do we have any strategy? So although things have questions, there's a too much of what to talk about, right. So, how the requirements are organized, how does know?

Okay, that's a completely different thing. But you know, you're still involved in the requirements to to understand the requirements if there are any deficient or complete defects in the requirements. I personally open communication requirement of Excel. Okay, so as a tester issue right the document issue does not have issues in the document. Okay, so that's the first thing that started start from the courts and then in the day okay this is more of a data spoken architecture right? architecture, data structures and all those stuff.

Here you will okay you will not be in one machaca mostly QA lead or no testers will not be that not busted? Do you need to get our information set like how the architecture is designed? Is it a snowflake schema? Is it a star schema? Where is the primary key going to this very foreign key is the candidate key is the natural key unit stage. In the design phase, you know, there's Okay, the real time it's completely different, it might not be distinct, but this is how it should be.

Normally it should be you know, everything is data modeling how there are no data Okay, so all the data modeling, data modeling is done okay. So all those things should be you know, to be known right we you have to know if you don't know those things if you don't know why which primary key is going to which foreign key and which foreign key is going to be your candidate key then you can perform this writing Write, write SQL, you can either test cases you can do nothing. Okay. So this is a you know, whether design part, you need to be involved and you know, you'd like more information on this and the implementation implementation, okay, let's see. Okay, I missed something here. Okay, in the requirements, that's fine.

Okay. You will be going in the design model to direct so there's so much work, right. Test Plan, document, test strategy document. Okay. So there are so many things. You need to write.

Okay. Whoa, okay. Let's In a design in the design phase we will be writing test plan document. Okay, test plan document and okay you will be helping us to do and we'll be working with all the information getting all the information from the architecture and we know you do reading test on up next implementation implementation Okay, developers will be writing code Okay, they'll be good to go. Now, let's say you have some time you will be writing a strategy document Okay, their strategy and test cases Okay, you'll be writing that time Okay. Now, you have covered all the two red design and non test testing something where you are going to test on this is know what the action shop but all the documentation part you have to complete that before you cannot wait till test right.

So you need to complete during the requirement design and implementation phase will be you know, finishing that into the story writing test plan, test strategy getting approval, you know, getting approval from the need, getting approval from your boss is getting approval from a viewer and getting you know finishing their work. And then the test you will be shot executing those test cases what you have written then installation installation phase is you know where you actually very good actually no migrate, okay now you put that all the information to the production, okay. You put in the production and it's already in the maintenance phase you have like if there is any production issues, or if there is any other issues. No, we'll be working on it. So, technically, testers will be involved in all of the phases. Okay.

No one will know if you say the thing like, testers jobs are from test and no testers will be idle in that case, then you know, it's not possible. You cannot be idle right. You will be what Something in somebody's face as a preparing test plan document a strategy document test cases attending meetings, you know, understanding the requirements, understanding the architecture, understanding all those things, so many things to do. Okay, any questions? So this is a DLC as well as waterfall. Three DLC is also same niche Okay, so this is all the same analysis design implementation, okay.

Planning analysis. So this is also like you know part of the waterfall you will want to fall for the delight from the sdlc any questions in this Michigan I think I missed something here. So, I said physical data modeling and physical data modeling and logical data model let me show you this we have five minutes we can work on that. We also have two documents PDM and helium I have that into this drive to shift forward in the physical data modeling right so, this is like you know, the more of a architecture point of view this should have I have information about this. So you have these three tables where the data is going okay. This is like very small Okay, this is not this.

Okay, this doesn't have this way. But you know, you will having more information PK primary key, okay, all this video is going so this is the table from We'll use a table and this is like you know this is pretty typical data modeling. So, this has all the information in this document okay this is this will be much more larger actually to be specific yeah this is good example right here you have this table range table supplier product category item okay and which this primary key going to this foreign key case foreign key okay. And this is primary key, okay. So, all the information if there is a candidate key candidate key there is no natural keys and obviously natural key all those information will be there this video physical data model, okay. So that is medium and you are more LTM that is logical data model.

So it contains the logical information of the conduct logical information. So, just like for example, so that's so physical Letterman. So one example is physical data where we have like tables or views are the example of logical progression. I don't know, if you have used then it's, it's a example. So this is like an example of logical data modeling. In real time, this might not be like this, it will be much more the document will be much more bigger.

You have more of a table level, okay? Everything will be in table level, in less of information level, okay, it's always it could be a graph making a chart, kind of chart kind of thing. Okay, so this is William. Okay. Tom, we're gonna use that. Okay.

Any questions in documentation and DLT Okay so how do you know this is a study to us should be when you do this you need to log into this okay? username is your email password is what you have set right for everyone has given no i Good luck on Okay, once you log in it you will be getting this notice page. Okay? You will be getting this page go here and click on it make a SharePoint that's it when you get this here you find feis. Okay. Go to files and upload your document and make sure your document name is no you should have that test plan underscore your name, okay underscore date.

So make sure so that you know, I understand who the test plan is, it will be so many people like maybe after the end make sure you follow that instruction or you I'm done in a rally, right? Just a rally. Okay, so that's it, we go your feet. Same again, read into this web page, go to it, make a SharePoint, that's it and you go to the files and upload it. That's it. Upload Files here, go upload advice and you can add points of his statement.

Okay? So that's how you can do it. That's it. There's no big deal in this okay? We don't have to worry about all other features. We don't require it.

We don't worry about digital only for how to upload and download okay? Because in real time we'll be using SharePoint. So as a as a lead, though, you'll be doing that. Okay. So does the region okay. We'll be working on it.

Okay, any questions? So it's already one your Waterford strength okay and we will be completing tomorrow and also the LD finishing this sdlc tomorrow okay. And spiral canonical, agile I'll be taking one class okay. So explaining the complete Agile process, how does it know what to do? completed by July 2, and he completely okay, so any questions, any suggestions, comments? Okay, so today we are going to connect close this class for today.

Okay, yeah thanks everyone.